summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/seccomp
diff options
context:
space:
mode:
authorBrian Norris <briannorris@chromium.org>2017-01-13 18:16:57 -0800
committerKalle Valo <kvalo@codeaurora.org>2017-01-20 11:47:23 +0200
commit0ed917d09d517646b4dffc96427e5a4cc14056de (patch)
tree5b47cb8bcf0f5109e4e188c435f73f7a2dac27b5 /tools/testing/selftests/seccomp
parentfe116788393942eef11d5c0f1cb16b1ef423970d (diff)
mwifiex: don't complain about 'unknown event id: 0x63'
Marvell folks tell me this is a debugging event that the driver doesn't need to handle, but on 8997 w/ firmware 16.68.1.p97, I see several of these sorts of messages at (for instance) boot time: [ 13.825848] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63 [ 14.838561] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63 [ 14.850397] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63 [ 32.529923] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63 Let's handle this "event" with a much lower verbosity. Signed-off-by: Brian Norris <briannorris@chromium.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'tools/testing/selftests/seccomp')
0 files changed, 0 insertions, 0 deletions