From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: akpm@linux-foundation.org, linville@tuxdriver.com, jgarzik@pobox.com
Subject: Re: net-2.6.24 plans
Date: Mon, 17 Sep 2007 14:18:26 -0700 (PDT) [thread overview]
Message-ID: <20070917.141826.70218261.davem@davemloft.net> (raw)
In-Reply-To: <20070916.202258.03371690.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Sun, 16 Sep 2007 20:22:58 -0700 (PDT)
> Tomorrow (Monday) I want to rebase the net-2.6.24 tree one more time
> to deal with all of the conflicts which exist between
> linux-2.6/net-2.6 and net-2.6.24, but I'll likely defer that
> until the net-2.6 fixes I just pushed to Linus are integrated.
I've just completed this rebase.
Andrew, I removed the troublesome IOAT patch. The only conflicts
and fixes you should need at this point are:
1) Removal of SET_MODULE_OWNER() from any extra drivers you import
into your tree.
2) dev_get_by_*() needs &init_net added as first parameter in any
other code you import outside of the net tree.
I guess a lot of this could be avoided if I simply merge in whatever
external stuff you're sucking in. 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.
I don't want to sound like a control freak or a whiner, but these
merge conflicts are growing painful at an astronomic rate and I'd
therefore prefer if we simply push everything through the net-2.6.24
tree from now until the merge window.
Today's rebase took several hours and it took significantly longer to
suck in Jeff's netdev tree over the weekend. I'm tired of playing
patch monkey, so I can sympathize with how life must be every day
for Andrew :-) But on a more serious note there are things I have
to actually hack on myself so anything that decreases the amount of
time I spend doing mindless patch whacking in the net-2.6.24 tree is
appreciated.
What say you?
next prev parent reply other threads:[~2007-09-17 21:18 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 [this message]
2007-09-17 21:40 ` Andrew Morton
2007-09-17 23:18 ` John W. Linville
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=20070917.141826.70218261.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linville@tuxdriver.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 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).