All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.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 10:54:55 -0500	[thread overview]
Message-ID: <20121126155455.GB27232@tuxdriver.com> (raw)
In-Reply-To: <50AE8BD3.8040902@broadcom.com>

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
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2012-11-26 16:01 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 [this message]
2012-11-26 20:54   ` 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=20121126155455.GB27232@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 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.