From: Arend van Spriel <arend@broadcom.com>
To: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
Cc: Kalle Valo <kvalo@codeaurora.org>, Pat Erley <pat-lkml@erley.org>,
<brudley@broadcom.com>, Franky Lin <frankyl@broadcom.com>,
<meuleman@broadcom.com>, <linville@tuxdriver.com>,
<pieterpg@broadcom.com>, <hdegoede@redhat.com>, <wens@csie.org>,
<linux-wireless@vger.kernel.org>,
<brcm80211-dev-list@broadcom.com>, <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] brcmfmac: avoid duplicated suspend/resume operation
Date: Mon, 16 Feb 2015 10:35:48 +0100 [thread overview]
Message-ID: <54E1B9F4.6090302@broadcom.com> (raw)
In-Reply-To: <54E19DA1.4030407@linux.intel.com>
On 02/16/15 08:34, Fu, Zhonghui wrote:
>
> On 2015/2/15 22:54, Kalle Valo wrote:
>> Arend van Spriel<arend@broadcom.com> writes:
>>
>>> On 02/15/15 04:27, Pat Erley wrote:
>>>> On 02/14/2015 08:40 PM, Fu, Zhonghui wrote:
>>>>> Any comments to this patch? Can it be accepted?
>>> I assume that patches are queued up until after the merge window that
>>> we are currently in.
>> That's right. In the future I will most likely apply patches also during
>> the merge window, but as I'm still a greenhorn I'll be on the safe and
>> wait for the merge window to end.
> I am very glad to see this.
> Could you please tell which release candidate this patch will be likely merged into now?
For which tree are you asking this? When the merge window ends and
linus' tree has moved to 3.20-rc1, the wireless-drivers-next will move
to that -rc1 as well and pending/accepted patches will be applied for
the next kernel release. If you are asking when they will be in linus'
tree than the answer is 3.21-rc1. Now if you say this patch solves a
real problem for you (providing usual proof like log with stack trace)
you can request it to go on the wireless-drivers tree to be fixed for 3.20.
Regards,
Arend
next prev parent reply other threads:[~2015-02-16 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 3:26 [PATCH v3] brcmfmac: avoid duplicated suspend/resume operation Fu, Zhonghui
2015-02-15 2:40 ` Fu, Zhonghui
2015-02-15 3:27 ` Pat Erley
2015-02-15 8:31 ` Arend van Spriel
2015-02-15 14:54 ` Kalle Valo
2015-02-16 7:34 ` Fu, Zhonghui
2015-02-16 9:35 ` Arend van Spriel [this message]
2015-02-27 7:53 ` Fu, Zhonghui
2015-02-27 9:08 ` Arend van Spriel
2015-03-02 15:08 ` Kalle Valo
2015-03-03 19:49 ` Arend van Spriel
2015-02-16 9:50 ` David Laight
2015-02-27 7:42 ` Fu, Zhonghui
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=54E1B9F4.6090302@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meuleman@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pat-lkml@erley.org \
--cc=pieterpg@broadcom.com \
--cc=wens@csie.org \
--cc=zhonghui.fu@linux.intel.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).