linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: David Shwatrz <dshwatrz@gmail.com>
Cc: Kalle Valo <kalle.valo@nokia.com>,
	Ivo van Doorn <ivdoorn@gmail.com>,
	johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: Where is allow-ap-vlan-modes.patch ?
Date: Mon, 10 Nov 2008 11:04:16 -0500	[thread overview]
Message-ID: <20081110160416.GI3546@tuxdriver.com> (raw)
In-Reply-To: <31436f4a0811100742p6154e2f9p34f3dfb1de2f71e3@mail.gmail.com>

On Mon, Nov 10, 2008 at 05:42:56PM +0200, David Shwatrz wrote:
> Hello,
> First, I hope you feel better soon.
> 
> Second:
> Looking at the patches at the mailing list, I do not see
> that anywhere it says against which git tree they were made.
> It could be : wireless-next-2.6,wireless-2.6, and wireless-testing.
> 
> I guess that there are many cases in which a patch can be applied to
> two of these trees (or maybe all three of them),
> whereas there are times in which it can be applied to only one git tree.
> 
> How is it determined to which tree the patches should be
> applied ?

I ask for people to send patches against wireless-testing in general.

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  reply	other threads:[~2008-11-10 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 15:01 Where is allow-ap-vlan-modes.patch ? David Shwatrz
2008-11-09 15:04 ` Ivo van Doorn
2008-11-09 15:16   ` Kalle Valo
2008-11-10  8:48   ` David Shwatrz
2008-11-10  9:02     ` Kalle Valo
2008-11-10 14:28       ` John W. Linville
2008-11-10 15:42         ` David Shwatrz
2008-11-10 16:04           ` John W. Linville [this message]
2008-11-10 18:54           ` Stefanik Gábor
2008-11-10 19:00             ` Luis R. Rodriguez

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=20081110160416.GI3546@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dshwatrz@gmail.com \
    --cc=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@nokia.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 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).