From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmsmac tx patches for 3.7
Date: Mon, 26 Nov 2012 21:54:10 +0100 [thread overview]
Message-ID: <50B3D6F2.3040701@broadcom.com> (raw)
In-Reply-To: <20121126155455.GB27232@tuxdriver.com>
On 11/26/2012 04:54 PM, John W. Linville wrote:
> On Thu, Nov 22, 2012 at 09:32:19PM +0100, Arend van Spriel wrote:
>
>> When Seth posted his rework on brcmsmac transmit, we had a number of
>> patches ready in the same area albeit less rigorous. With Seth's patches
>> lined up in wireless-next for 3.8, I am wondering what to do here.
>> Should I send our patches against the wireless tree? These patches will
>> definitely result in conflicts when merging to wireless-next, which you
>> typically do. Actually, we do not want these patches in wireless-next as
>> rework from Seth makes them irrelevant.
>>
>> Any advice on this?
>
> If they are fixes, then they should be small and obvious -- hopefully
> that makes the merging relatively easy? You might try applying
> them to a local wireless tree and pulling that into a local copy of
> wireless-next, then resolving the conflicts locally so that you can
> give me some idea of any tricky merges?
>
> John
>
Hi John,
I did already (re)submit the one 3.7 patch to you fixing a slab
corruption. As the code is reworked pretty significantly (removing
packets queues) in 3.8, I have a similar patch for 3.8 that I intend to
submit soon. So merge of the 3.7 patch can be ignored for wireless-next.
Gr. AvS
prev parent reply other threads:[~2012-11-26 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 20:32 brcmsmac tx patches for 3.7 Arend van Spriel
2012-11-26 15:54 ` John W. Linville
2012-11-26 20:54 ` Arend van Spriel [this message]
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=50B3D6F2.3040701@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).