From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kvalo@adurom.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
Piotr Haber <phaber@broadcom.com>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: [PATCH V2 v3.7] brcmsmac: handle packet drop on enqueuing correctly
Date: Mon, 3 Dec 2012 13:39:13 -0500 [thread overview]
Message-ID: <20121203183912.GE26027@tuxdriver.com> (raw)
In-Reply-To: <871uf7w6w0.fsf@purkki.adurom.net>
On Mon, Dec 03, 2012 at 04:24:31PM +0200, Kalle Valo wrote:
> Hi Arend,
>
> "Arend van Spriel" <arend@broadcom.com> writes:
>
> > What is keeping you from picking up this patch? Anything I should do?
> > This V2 removed the no-op changes in ampdu.c that Seth indicated so...
>
> Most likely it's too late. Dave already told that that John's previous
> pull request might not make it to 3.7.
Yes, that. Also, given the merge difficulties this creates and the
fact that Seth's patch is already queued for 3.8, maybe you should
consider sending this for the 3.7 stable series when it opens?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-12-03 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 20:23 [PATCH V2 v3.7] brcmsmac: handle packet drop on enqueuing correctly Arend van Spriel
2012-12-03 8:33 ` Arend van Spriel
2012-12-03 14:24 ` Kalle Valo
2012-12-03 18:39 ` John W. Linville [this message]
2012-12-03 18:54 ` Arend van Spriel
2012-12-03 18:59 ` John W. Linville
2012-12-04 19:52 ` Arend van Spriel
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=20121203183912.GE26027@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=phaber@broadcom.com \
--cc=seth.forshee@canonical.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).