From: "David S. Miller" <davem@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
trivial@rustcorp.com.au
Subject: Re: [TRIVIAL] Fix initialization sequence in SunGEM driver
Date: Thu, 9 Oct 2003 23:56:53 -0700 [thread overview]
Message-ID: <20031009235653.26e509c1.davem@redhat.com> (raw)
In-Reply-To: <20031009070649.GA830@zax>
Applied, thanks David.
But in the future please send net driver fixes to netdev@oss.sgi.com
with either Jeff Garzik or myself CC:'d? Thanks.
I also would absolutely not classify your patch as "trivial".
It's not like a missing semi-colon or a comment typo, someone
with real understanding of how this stuff works would need to
review this patch.
Based just upon the kinds of networking patches Linus has forwarded
to me today, I can duly say that far too much stuff is being sent
as "[TRIVIAL]" which is not.
next prev parent reply other threads:[~2003-10-10 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 7:06 [TRIVIAL] Fix initialization sequence in SunGEM driver David Gibson
2003-10-10 6:56 ` David S. Miller [this message]
2003-10-24 3:30 ` Rusty Russell
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=20031009235653.26e509c1.davem@redhat.com \
--to=davem@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.au \
/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