From: Andrew Morton <akpm@linux-foundation.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
netdev@vger.kernel.org, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sb1250-mac: Driver model & phylib update
Date: Fri, 28 Sep 2007 11:39:45 -0700 [thread overview]
Message-ID: <20070928113945.389a6a70.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0709281628130.10439@blysk.ds.pg.gda.pl>
On Fri, 28 Sep 2007 17:23:00 +0100 (BST) "Maciej W. Rozycki" <macro@linux-mips.org> wrote:
> On Mon, 24 Sep 2007, Andrew Morton wrote:
>
> > > Well, this is against Jeff's netdev-2.6 tree which hopefully is not as
> > > crufty as Linus's old mainline; if it is not possible to queue this change
> > > for 2.6.25 or suchlike, then I will try to resubmit later.
> >
> > Most of Jeff's netdev tree got dumped into Dave's net-2.6.24 tree. That's
> > the one you want to be raising patches against for the next few weeks.
>
> OK, thanks for clarification. Then both patches already submitted:
>
> patch-netdev-2.6.23-rc6-20070920-sb1250-mac-typedef-9
> patch-netdev-2.6.23-rc6-20070920-sb1250-mac-29
>
> apply cleanly to net-2.6.24 one on top of the other in this order.
<checks the netdev archives>
hm, I found a patch at the end of an email trail which is datestamped Sep
20 here which appears to match the first one you mentioned, but I'm having
trouble working out what patch subject your "sb1250-mac" maps onto.
This is why I make the patch filenames map directly from the patch titles,
so I end up with files like
optimize-x86-page-faults-like-all-other-achitectures-and-kill-notifier-cruft.patch.
Verbose, but it reduces confusion and mistakes.
> I can resubmit them
That's always a good choice. Patches which are dangling at the end of an email
discussion often don't get merged: it is unclear to the receiveing party that
the discussion has terminated, and I'm never terribly confident in the testing
level of a patch which obviously got modified two minutes before it was sent.
> -- where? netdev? As I say I am fine with 2.6.25 as
> the target.
jeff, netdev, me?
next prev parent reply other threads:[~2007-09-28 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 11:52 [PATCH] sb1250-mac: Driver model & phylib update Maciej W. Rozycki
2007-09-21 19:44 ` Andrew Morton
2007-09-24 14:41 ` Maciej W. Rozycki
2007-09-24 16:55 ` Andrew Morton
2007-09-28 16:23 ` Maciej W. Rozycki
2007-09-28 18:39 ` Andrew Morton [this message]
2007-09-25 13:18 ` Ralf Baechle
2007-09-25 16:18 ` Andrew Morton
2007-09-29 5:15 ` Jeff Garzik
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=20070928113945.389a6a70.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox