diff options
| author | Emmanuel Grumbach <[email protected]> | 2015-01-29 14:58:20 +0200 |
|---|---|---|
| committer | Emmanuel Grumbach <[email protected]> | 2015-03-02 08:20:28 +0200 |
| commit | b6eaa45aa18bf010fd54cdac0e3007dfdd7f3f8a (patch) | |
| tree | 69869fec6604ece7ef73c1a6c1395231d7c8a3dd /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | d2709ad723ff2ae22013978ed6ec29cf1b9b8332 (diff) | |
iwlwifi: mvm: add the cause of the firmware dump in the dump
Now that the firmware dump can be triggered by events in
the code and not only the user or an firmware ASSERT, we
need a way to know why the firmware dump was triggered.
Add a section in the dump file for that.
Signed-off-by: Emmanuel Grumbach <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions