From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Andrew Morton <akpm@osdl.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Greg KH <greg@kroah.com>,
Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH -mm] PM: add /sys/power documentation to Documentation/ABI
Date: Wed, 30 Aug 2006 15:03:58 -0700 [thread overview]
Message-ID: <20060830150358.55233204.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060830144350.3b9bb273.akpm@osdl.org>
On Wed, 30 Aug 2006 14:43:50 -0700 Andrew Morton wrote:
> On Wed, 30 Aug 2006 23:38:06 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > Documentation/ABI/testing
>
> psst, Greg, they're still sending too much stuff: need more paperwork!
>
> Some words about this in Documentation/SubmitChecklist would be nice.
and people actually using it would be nice(r).
Is this close to what you are looking for?
---
From: Randy Dunlap <rdunlap@xenotime.net>
Mention Documenation/ABI/ requirements in Documentation/SubmitChecklist.
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
Documentation/SubmitChecklist | 3 +++
1 files changed, 3 insertions(+)
--- linux-2618-rc5all.orig/Documentation/SubmitChecklist
+++ linux-2618-rc5all/Documentation/SubmitChecklist
@@ -61,3 +61,6 @@ kernel patches.
Documentation/kernel-parameters.txt.
18: All new module parameters are documented with MODULE_PARM_DESC()
+
+19: All new userspace interfaces are documented in Documentation/ABI/.
+ See Documentation/ABI/README for more information.
next prev parent reply other threads:[~2006-08-30 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 21:38 Rafael J. Wysocki
2006-08-30 21:35 ` Pavel Machek
2006-08-30 21:43 ` Andrew Morton
2006-08-30 22:03 ` Randy.Dunlap [this message]
2006-08-30 22:32 ` Andrew Morton
2006-08-30 22:51 ` Greg KH
2006-08-30 22:04 ` Pavel Machek
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=20060830150358.55233204.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®