From: "John W. Linville" <linville@tuxdriver.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: net-2.6.24 plans
Date: Mon, 17 Sep 2007 19:18:30 -0400 [thread overview]
Message-ID: <20070917231830.GG9282@tuxdriver.com> (raw)
In-Reply-To: <20070917144037.100b3fc1.akpm@linux-foundation.org>
On Mon, Sep 17, 2007 at 02:40:37PM -0700, Andrew Morton wrote:
> On Mon, 17 Sep 2007 14:18:26 -0700 (PDT)
> David Miller <davem@davemloft.net> wrote:
> > I guess a lot of this could be avoided if I simply merge in whatever
> > external stuff you're sucking in.
> plus boatloads of stuff in wireless.
>
> > I imagine this is just one of
> > Linville's trees (I'm surprised that hasn't been sent to me frankly)
> > and some specific new drivers you're merging in.
The stuff in wireless-dev is a collection of drivers (some of which
probably should be merged now) and some mac80211 gorp that is not
yet merge-worthy. Trust me, I'm trying to get as many items out of
it as possible.
> Yeah, git-net versus git-wireless isn't pretty. The huge amount of pending
> wireless stuff has been a bit of a nuisance for some months. But it's
> probably a bigger nuisance for John ;)
Yeah...<sigh>...yeah...<sigh>...yeah... :-(
But as hch would surely point-out, it is my own laziness at fault...and
driver authors who tremble in fear when I mention merging their
drivers upstream...but, I digress... :-)
I just (minutes ago) finished the mop-up of the patch mess which
had accumulated on me during my KS-related travel and the subsequent
period of catching-up. (I'm sure I still missed something or botched
something). I think I can get an -mm suitable patch together within
the next few hours.
John
P.S. Andrew, I'll send you a link to a new git-wireless.patch --
I'm sure you don't want a complicated git invocation... Until then,
I don't think you should try pulling wireless-dev...
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-09-17 23:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 3:22 net-2.6.24 plans David Miller
2007-09-17 4:10 ` Jeff Garzik
2007-09-17 16:22 ` David Miller
2007-09-17 21:18 ` David Miller
2007-09-17 21:40 ` Andrew Morton
2007-09-17 23:18 ` John W. Linville [this message]
2007-09-17 23:42 ` David Miller
2007-09-17 23:49 ` Andrew Morton
2007-09-18 3:23 ` John W. Linville
2007-09-19 1:27 ` John W. Linville
2007-09-19 21:07 ` John W. Linville
2007-09-19 22:19 ` David Miller
2007-09-20 14:17 ` John W. Linville
2007-09-20 14:50 ` Johannes Berg
2007-09-20 16:56 ` John W. Linville
2007-09-20 19:50 ` John W. Linville
2007-09-17 23:39 ` David Miller
2007-09-17 23:53 ` Andrew Morton
2007-09-18 0:15 ` David Miller
2007-09-18 1:51 ` David Miller
2007-09-18 2:13 ` Andy Gospodarek
2007-09-18 3:20 ` John W. Linville
2007-09-17 23:57 ` Nelson, Shannon
2007-09-18 0:04 ` Andrew Morton
2007-09-18 0:04 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 9:36 David Miller
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=20070917231830.GG9282@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--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.