From: "John W. Linville" <linville@tuxdriver.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please pull 'iwlwifi' branch of wireless-2.6
Date: Wed, 19 Sep 2007 10:57:50 -0400 [thread overview]
Message-ID: <20070919145749.GA5483@tuxdriver.com> (raw)
In-Reply-To: <46F12414.8000900@garzik.org>
On Wed, Sep 19, 2007 at 09:28:52AM -0400, Jeff Garzik wrote:
> David Miller wrote:
> >Jeff, if you have no objections I'll pull this into net-2.6.24
> Given that there is now a large backlog of new drivers to review, I
> think the preferred course of action would be to queue them into -mm
> (via net-2.6.24) for wider review and testing, and then make sure they
> all get a thorough review+ACK before pushing upstream.
FWIW, all of the wireless drivers posted recently have been in -mm
for some time thanks to Andrew's pulls of wireless-dev.
> So far, its sounding like each review has turned up stuff that wants
> fixing before the drivers commented upon go upstream.
I'm sure there are things worth fixing. Feel free to comment and
I/we will scramble to make the appropriate changes.
John
--
John W. Linville
linville@tuxdriver.com
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Please pull 'iwlwifi' branch of wireless-2.6
Date: Wed, 19 Sep 2007 10:57:50 -0400 [thread overview]
Message-ID: <20070919145749.GA5483@tuxdriver.com> (raw)
In-Reply-To: <46F12414.8000900-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
On Wed, Sep 19, 2007 at 09:28:52AM -0400, Jeff Garzik wrote:
> David Miller wrote:
> >Jeff, if you have no objections I'll pull this into net-2.6.24
> Given that there is now a large backlog of new drivers to review, I
> think the preferred course of action would be to queue them into -mm
> (via net-2.6.24) for wider review and testing, and then make sure they
> all get a thorough review+ACK before pushing upstream.
FWIW, all of the wireless drivers posted recently have been in -mm
for some time thanks to Andrew's pulls of wireless-dev.
> So far, its sounding like each review has turned up stuff that wants
> fixing before the drivers commented upon go upstream.
I'm sure there are things worth fixing. Feel free to comment and
I/we will scramble to make the appropriate changes.
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
next prev parent reply other threads:[~2007-09-19 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 18:50 Please pull 'iwlwifi' branch of wireless-2.6 John W. Linville
2007-09-18 18:50 ` John W. Linville
2007-09-18 19:22 ` David Miller
2007-09-18 19:22 ` David Miller
2007-09-19 13:28 ` Jeff Garzik
2007-09-19 13:28 ` Jeff Garzik
2007-09-19 14:57 ` John W. Linville [this message]
2007-09-19 14:57 ` John W. Linville
2007-09-19 10:13 ` Christoph Hellwig
2007-09-21 1:20 ` Zhu Yi
2007-09-21 1:20 ` Zhu Yi
2007-09-21 1:34 ` John W. Linville
2007-09-26 2:31 ` David Miller
2007-09-21 8:05 ` Christoph Hellwig
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=20070919145749.GA5483@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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.