From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: kernel-doc-patches for linux-next
Date: Wed, 14 Sep 2011 17:03:30 -0700 [thread overview]
Message-ID: <4E7140D2.8050804@xenotime.net> (raw)
Hi Stephen,
Please grab the quilt queue of kernel-doc-patches from
http://www.xenotime.net/kernel-doc-patches/current/
until kernel.org returns.
thanks,
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next reply other threads:[~2011-09-15 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 0:03 Randy Dunlap [this message]
2011-09-15 1:02 ` kernel-doc-patches for linux-next Stephen Rothwell
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=4E7140D2.8050804@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.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