From: Jeff Garzik <garzik@havoc.gtf.org>
To: Urban Widmark <urban@teststation.com>
Cc: "Ivan G." <ivangurdiev@yahoo.com>,
Shing Chuang <ShingChuang@via.com.tw>,
LKML <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: [PATCH] Via-rhine minor issues
Date: Sun, 21 Apr 2002 12:07:10 -0400 [thread overview]
Message-ID: <20020421120710.H2301@havoc.gtf.org> (raw)
In-Reply-To: <02042101022001.00833@cobra.linux> <Pine.LNX.4.33.0204211151010.13036-100000@cola.teststation.com>
On Sun, Apr 21, 2002 at 12:19:40PM +0200, Urban Widmark wrote:
> On Sun, 21 Apr 2002, Ivan G. wrote:
>
> > DIFF-ED AGAINST:
> > 2.4.19-pre3 ( I don't think there were changes to via-rhine
> > b-ween pre3 and pre7)
>
> You should probably send this to Jeff Garzik instead of Marcelo. Jeff
> collects net driver patches.
>
> If you don't, Shing Chuang's changes are in -pre7-ac2, so a re-diff vs
> that and seding it to Alan Cox may cause less merge work.
Does Ivan's patch look ok to you, Urban? I'd like to get your initial
sign-off on it. From a quick look, it looks ok to me.
And yes, you are correct: my preference would be to receive two
submissions in my inbox: Shing Chuang's patch, and then Ivan's patch
(less Shing's work).
If there are multiple issues, multiple patches are encouraged. More
split-up is always better than less. :)
Regards,
Jeff
next prev parent reply other threads:[~2002-04-21 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 7:02 [PATCH] Via-rhine minor issues Ivan G.
2002-04-21 10:00 ` Martin Eriksson
2002-04-21 10:19 ` Urban Widmark
2002-04-21 16:07 ` Jeff Garzik [this message]
2002-04-21 21:16 Ivan G.
2002-04-21 23:02 ` your mail Jeff Garzik
2002-04-21 23:25 ` [PATCH] Via-rhine minor issues Ivan G.
2002-04-22 19:33 ` Urban Widmark
2002-04-23 4:07 ` Ivan G.
2002-04-23 13:44 ` Urban Widmark
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=20020421120710.H2301@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=ShingChuang@via.com.tw \
--cc=ivangurdiev@yahoo.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=urban@teststation.com \
/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).