All of lore.kernel.org
 help / color / mirror / Atom feed
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: brcmsmac tx patches for 3.7
Date: Thu, 22 Nov 2012 21:32:19 +0100	[thread overview]
Message-ID: <50AE8BD3.8040902@broadcom.com> (raw)

Hi John,

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?

Gr. AvS


             reply	other threads:[~2012-11-22 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 20:32 Arend van Spriel [this message]
2012-11-26 15:54 ` brcmsmac tx patches for 3.7 John W. Linville
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=50AE8BD3.8040902@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 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.