Re: [PATCH v3] brcmfmac: avoid duplicated suspend/resume operation
From: Arend van Spriel
Date: Mon Feb 16 2015 - 04:35:59 EST
On 02/16/15 08:34, Fu, Zhonghui wrote:
On 2015/2/15 22:54, Kalle Valo wrote:
Arend van Spriel<arend@xxxxxxxxxxxx> writes:
I am very glad to see this.
On 02/15/15 04:27, Pat Erley wrote:
That's right. In the future I will most likely apply patches also during
On 02/14/2015 08:40 PM, Fu, Zhonghui wrote:
I assume that patches are queued up until after the merge window that
Any comments to this patch? Can it be accepted?
we are currently in.
the merge window, but as I'm still a greenhorn I'll be on the safe and
wait for the merge window to end.
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/