From: Rob Landley <landley@webofficenow.com>
To: "Craig Lyons" <craigl@promise.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Getting A Patch Into The Kernel
Date: Tue, 12 Jun 2001 14:32:31 -0400 [thread overview]
Message-ID: <01061214323100.01850@localhost.localdomain> (raw)
In-Reply-To: <005101c0f38f$e2000960$bd01a8c0@promise.com>
In-Reply-To: <005101c0f38f$e2000960$bd01a8c0@promise.com>
On Tuesday 12 June 2001 18:34, Craig Lyons wrote:
> We have a patch that fixes this and are wondering if it
> is possible to get this patch into the kernel, and if so, how this would be
> done?
Well, you start by reading this:
http://www.linuxhq.com/kernel/v2.4/doc/SubmittingPatches.html
Which basically says that you post it here, with a title along the lines of:
"[PATCH] promise IDE raid support".
Start the body of your email with a brief description of the patch (the above
is fine, mentioning that this is an official patch from promise is nice), and
then include the patch itself at the end of the email in plain text. (Linus
won't read Mime attachments, although others sometimes do and forward them to
him. Sometimes.)
You do know how to make a unified diff using "diff -u", right? (I'm assuming
you have an includeable patch already prepared?)
Also, try to use an email program that doesn't mangle whitespace. (It's a
nit-pick, but it's good hygiene.) The difference between spaces and tabs is
generally considered to be a good thing to maintain.
Rob
next prev parent reply other threads:[~2001-06-12 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 22:34 Getting A Patch Into The Kernel Craig Lyons
2001-06-12 18:32 ` Rob Landley [this message]
2001-06-12 23:21 ` Robert Love
2001-06-13 0:34 ` Rik van Riel
2001-06-13 23:18 ` Alan Cox
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=01061214323100.01850@localhost.localdomain \
--to=landley@webofficenow.com \
--cc=craigl@promise.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.