summaryrefslogtreecommitdiffstats
path: root/drivers/soc
diff options
context:
space:
mode:
authorVladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>2014-08-11 03:29:57 -0700
committerJohannes Berg <johannes.berg@intel.com>2014-08-26 11:15:58 +0200
commit970fdfa89babb5a6f1a3d345e8cb54d92c1e3a8f (patch)
tree05baa20b3aede4591303a27b6581a9fbd79037d8 /drivers/soc
parent649b2a4da5d8a39c4d7be2fd228cf797819656f9 (diff)
downloadtalos-op-linux-970fdfa89babb5a6f1a3d345e8cb54d92c1e3a8f.tar.gz
talos-op-linux-970fdfa89babb5a6f1a3d345e8cb54d92c1e3a8f.zip
cfg80211: remove @gfp parameter from cfg80211_rx_mgmt()
In the cfg80211_rx_mgmt(), parameter @gfp was used for the memory allocation. But, memory get allocated under spin_lock_bh(), this implies atomic context. So, one can't use GFP_KERNEL, only variants with no __GFP_WAIT. Actually, in all occurrences GFP_ATOMIC is used (wil6210 use GFP_KERNEL by mistake), and it should be this way or warning triggered in the memory allocation code. Remove @gfp parameter as no actual choice exist, and use hard coded GFP_ATOMIC for memory allocation. Signed-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'drivers/soc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud