diff options
| author | Christophe JAILLET <[email protected]> | 2020-07-22 12:17:01 +0200 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2020-08-02 18:19:03 +0300 |
| commit | 9130559cf8dbc34b3d54a2ab5f2a746b964c46a4 (patch) | |
| tree | 4b97a62b9edf2a962df272104dc44259b3d9e269 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 99aaa1aafa5c745c0d01f6f980f990ed0edd88ba (diff) | |
ipw2100: Use GFP_KERNEL instead of GFP_ATOMIC in some memory allocation
The call chain is:
ipw2100_pci_init_one (the probe function)
--> ipw2100_queues_allocate
--> ipw2100_tx_allocate
No lock is taken in the between.
So it is safe to use GFP_KERNEL in 'ipw2100_tx_allocate()'.
BTW, 'ipw2100_queues_allocate()' also calls 'ipw2100_msg_allocate()' which
already allocates some memory using GFP_KERNEL.
Signed-off-by: Christophe JAILLET <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions