From: Rusty Russell <rusty@rustcorp.com.au>
To: "David S. Miller" <davem@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] Fix initialization sequence in SunGEM driver
Date: Fri, 24 Oct 2003 13:30:02 +1000 [thread overview]
Message-ID: <20031024063847.40F3C2C0F1@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 09 Oct 2003 23:56:53 MST." <20031009235653.26e509c1.davem@redhat.com>
In message <20031009235653.26e509c1.davem@redhat.com> you write:
> 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.
Perhaps. Certainly I give more slack to a trusted source, and since I
end up just sending it to the maintainer anyway, I don't usually see
too much harm in holding it. Perhaps I need a non-trivial patch
monkey 8)
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2003-10-24 6:38 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
2003-10-24 3:30 ` Rusty Russell [this message]
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=20031024063847.40F3C2C0F1@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=davem@redhat.com \
--cc=david@gibson.dropbear.id.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