summaryrefslogtreecommitdiffstats
path: root/fs/romfs
diff options
context:
space:
mode:
authorArend van Spriel <arend@broadcom.com>2014-09-12 16:19:30 +0200
committerJohn W. Linville <linville@tuxdriver.com>2014-09-15 21:09:26 +0200
commit87c4790330810fe5caf0172d9320cf24ef19cebe (patch)
tree751d6c86a04078c207b0396bf60e723221b342b7 /fs/romfs
parentbrcmfmac: obtain ifp through wdev structure (diff)
downloadlinux-87c4790330810fe5caf0172d9320cf24ef19cebe.tar.xz
linux-87c4790330810fe5caf0172d9320cf24ef19cebe.zip
brcmfmac: handle IF event for P2P_DEVICE interface
The firmware notifies about interface changes through the IF event which has a NO_IF flag that means host can ignore the event. This behaviour was introduced in the driver by: commit 2ee8382fc6c763c76396a6aaff77a27089eed3aa Author: Arend van Spriel <arend@broadcom.com> Date: Sat Aug 10 12:27:24 2013 +0200 brcmfmac: ignore IF event if firmware indicates it It turns out that the IF event for the P2P_DEVICE also has this flag set, but the event should not be ignored in this scenario. The mentioned commit caused a regression in 3.12 kernel in creation of the P2P_DEVICE interface. Cc: <stable@vger.kernel.org> # 3.14, 3.16 Reviewed-by: Hante Meuleman <meuleman@broadcom.com> Reviewed-by: Franky (Zhenhui) Lin <frankyl@broadcom.com> Reviewed-by: Daniel (Deognyoun) Kim <dekim@broadcom.com> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com> Signed-off-by: Arend van Spriel <arend@broadcom.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'fs/romfs')
0 files changed, 0 insertions, 0 deletions