From: Kalle Valo <kvalo@codeaurora.org> To: "Rafał Miłecki" <zajec5@gmail.com> Cc: Brett Rudley <brudley@broadcom.com>, Arend van Spriel <arend@broadcom.com>, "Franky \(Zhenhui\) Lin" <frankyl@broadcom.com>, Hante Meuleman <meuleman@broadcom.com>, Pieter-Paul Giesberts <pieterpg@broadcom.com>, Franky Lin <franky.lin@broadcom.com>, "linux-wireless\@vger.kernel.org" <linux-wireless@vger.kernel.org>, brcm80211 development <brcm80211-dev-list@broadcom.com>, Network Development <netdev@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH 4.7 FIX] brcmfmac: fix lockup when removing P2P interface after event timeout Date: Fri, 17 Jun 2016 12:49:19 +0300 [thread overview] Message-ID: <87h9csuov4.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <CACna6rym3y0sqAUptgnt-mUiBidFGzVAzw4XcYr95q6MD2r5yw@mail.gmail.com> (=?utf-8?Q?=22Rafa=C5=82_Mi=C5=82ecki=22's?= message of "Fri, 17 Jun 2016 07:33:20 +0200") Rafał Miłecki <zajec5@gmail.com> writes: >>>> Failed to apply, please rebase: >>>> >>>> Applying: brcmfmac: fix lockup when removing P2P interface after event timeout >>>> Using index info to reconstruct a base tree... >>>> Falling back to patching base and 3-way merge... >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.h >>>> CONFLICT (content): Merge conflict in drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.h >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c >>>> Failed to merge in the changes. >>>> Patch failed at 0001 brcmfmac: fix lockup when removing P2P interface after event timeout >>> >>> What tree did you try it on? >>> >>> I just went into a dir where I have cloned: >>> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git >>> >>> My HEAD commit is: >>> 034fdd4 Merge ath-current from ath.git >>> >>> And I can apply this patch cleanly doing: >>> curl https://patchwork.kernel.org/patch/9138925/mbox/ | git am >> >> I was trying to apply this to wireless-drivers-next. I didn't get a >> confirmation from Arend and I didn't consider the fix important enough >> for 4.7. But of course I can reconsider if needed. > > I think I agree it won't hurt to get it into -next. Noone earlier > reported this bug and it seems to be there for a long time. Also > applying it to -next will allow avoiding merge conflicts and immediate > development work on -next. Exactly, there is a cost when taking patches to wireless-drivers.git and that's why I try to keep the bar high. Regressions and user reported bugs take priority, other fixes are handled case by case. > I'll resend this patch rebased on -next soon. Thanks. -- Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> To: "Rafał Miłecki" <zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: Brett Rudley <brudley-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>, Arend van Spriel <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>, "Franky \(Zhenhui\) Lin" <frankyl-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>, Hante Meuleman <meuleman-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>, Pieter-Paul Giesberts <pieterpg-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>, Franky Lin <franky.lin-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>, "linux-wireless\@vger.kernel.org" <linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, brcm80211 development <brcm80211-dev-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>, Network Development <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Linux Kernel Mailing List <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: Re: [PATCH 4.7 FIX] brcmfmac: fix lockup when removing P2P interface after event timeout Date: Fri, 17 Jun 2016 12:49:19 +0300 [thread overview] Message-ID: <87h9csuov4.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <CACna6rym3y0sqAUptgnt-mUiBidFGzVAzw4XcYr95q6MD2r5yw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (=?utf-8?Q?=22Rafa=C5=82_Mi=C5=82ecki=22's?= message of "Fri, 17 Jun 2016 07:33:20 +0200") Rafał Miłecki <zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: >>>> Failed to apply, please rebase: >>>> >>>> Applying: brcmfmac: fix lockup when removing P2P interface after event timeout >>>> Using index info to reconstruct a base tree... >>>> Falling back to patching base and 3-way merge... >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.h >>>> CONFLICT (content): Merge conflict in drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.h >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c >>>> Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c >>>> Failed to merge in the changes. >>>> Patch failed at 0001 brcmfmac: fix lockup when removing P2P interface after event timeout >>> >>> What tree did you try it on? >>> >>> I just went into a dir where I have cloned: >>> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git >>> >>> My HEAD commit is: >>> 034fdd4 Merge ath-current from ath.git >>> >>> And I can apply this patch cleanly doing: >>> curl https://patchwork.kernel.org/patch/9138925/mbox/ | git am >> >> I was trying to apply this to wireless-drivers-next. I didn't get a >> confirmation from Arend and I didn't consider the fix important enough >> for 4.7. But of course I can reconsider if needed. > > I think I agree it won't hurt to get it into -next. Noone earlier > reported this bug and it seems to be there for a long time. Also > applying it to -next will allow avoiding merge conflicts and immediate > development work on -next. Exactly, there is a cost when taking patches to wireless-drivers.git and that's why I try to keep the bar high. Regressions and user reported bugs take priority, other fixes are handled case by case. > I'll resend this patch rebased on -next soon. Thanks. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-17 9:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-27 19:53 [PATCH 4.7 FIX] brcmfmac: fix lockup when removing P2P interface after event timeout Rafał Miłecki 2016-06-02 9:42 ` Kalle Valo 2016-06-16 15:10 ` Kalle Valo 2016-06-17 4:59 ` Rafał Miłecki 2016-06-17 5:13 ` Kalle Valo 2016-06-17 5:33 ` Rafał Miłecki 2016-06-17 9:49 ` Kalle Valo [this message] 2016-06-17 9:49 ` Kalle Valo 2016-06-17 10:29 ` [PATCH REBASED] " Rafał Miłecki 2016-06-29 15:57 ` [REBASED] " Kalle Valo 2016-06-17 10:48 ` [PATCH] brcmfmac: use const char * for interface name in brcmf_add_if Rafał Miłecki 2016-06-17 11:23 ` Joe Perches 2016-06-17 11:23 ` Joe Perches 2016-06-29 16:00 ` Kalle Valo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=87h9csuov4.fsf@kamboji.qca.qualcomm.com \ --to=kvalo@codeaurora.org \ --cc=arend@broadcom.com \ --cc=brcm80211-dev-list@broadcom.com \ --cc=brudley@broadcom.com \ --cc=franky.lin@broadcom.com \ --cc=frankyl@broadcom.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-wireless@vger.kernel.org \ --cc=meuleman@broadcom.com \ --cc=netdev@vger.kernel.org \ --cc=pieterpg@broadcom.com \ --cc=zajec5@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.