From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 6/8] docs: add URL for paper on submitting patches
Date: Thu, 09 Oct 2008 16:52:35 -0700 [thread overview]
Message-ID: <12235963552620@xenotime.net> (raw)
In-Reply-To: <12235963551043@xenotime.net>
From: Andi Kleen <ak@linux.intel.com>
Add a reference to paper to SubmittingPatches
For this year's OLS I wrote a paper on successfull strategies
to submit difficult kernel patches. Add a reference to it to
SubmittingPatches.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/SubmittingPatches | 5 +++++
1 file changed, 5 insertions(+)
--- linux-2.6.27-rc9-git2.orig/Documentation/SubmittingPatches
+++ linux-2.6.27-rc9-git2/Documentation/SubmittingPatches
@@ -672,4 +672,9 @@ Kernel Documentation/CodingStyle:
Linus Torvalds's mail on the canonical patch format:
<http://lkml.org/lkml/2005/4/7/183>
+
+Andi Kleen, "On submitting kernel patches"
+ Some strategies to get difficult or controversal changes in.
+ http://halobates.de/on-submitting-patches.pdf
+
--
--
next prev parent reply other threads:[~2008-10-09 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 23:52 [PATCH 1/8 for 2.6.27] docs: fix uvesafb mode_option Randy Dunlap
2008-10-09 23:52 ` [PATCH 2/8] docs: fix CDROM missing test program reference Randy Dunlap
2008-10-09 23:52 ` [PATCH 3/8] docs: fix ramfs hello program build name Randy Dunlap
2008-10-09 23:52 ` Randy Dunlap [this message]
2008-10-09 23:52 ` [PATCH 5/8] docs: add printk lib. extensions Randy Dunlap
2008-10-09 23:52 ` [PATCH 8/8] docs: fix docbook cmd output alignment Randy Dunlap
2008-10-09 23:52 ` [PATCH 4/8] docs: fix ManagementStyle book name Randy Dunlap
2008-10-09 23:52 ` [PATCH 7/8] docs: fix Doc/x86/ subdir references Randy Dunlap
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=12235963552620@xenotime.net \
--to=rdunlap@xenotime.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox