From: James Bottomley <James.Bottomley@steeleye.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] aeventd logging application (Part 1)
Date: 13 Feb 2004 17:04:44 -0500 [thread overview]
Message-ID: <1076709884.2159.415.camel@mulgrave> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F2552AD@otce2k03.adaptec.com>
On Fri, 2004-02-13 at 16:48, Salyzyn, Mark wrote:
> I expect this to be rejected for inclusion to the kernel source tree ...
> in that case the patch may just be done standalone (patch -p5).
Well, I can satisfy your expectation on that score ;-)
The rule is no user level tools at all in the kernel that aren't
necessary for the kernel compile, no matter how closely they're tied to
the kernel's operation. Even things like udev don't get to go into the
kernel sources.
James
next prev parent reply other threads:[~2004-02-13 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 21:48 [PATCH] aeventd logging application (Part 1) Salyzyn, Mark
2004-02-13 22:04 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 22:40 Salyzyn, Mark
2004-02-13 23:04 ` Christoph Hellwig
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=1076709884.2159.415.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.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