From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com,
gregkh@linuxfoundation.org, x86@kernel.org
Subject: Re: [PATCH] Documentation and source code comments updates (v1)
Date: Tue, 26 Feb 2013 11:40:34 -0500 [thread overview]
Message-ID: <20130226164034.GE15154@phenom.dumpdata.com> (raw)
In-Reply-To: <1361855296.27287.7@driftwood>
On Mon, Feb 25, 2013 at 11:08:16PM -0600, Rob Landley wrote:
> On 02/25/2013 02:54:07 PM, Konrad Rzeszutek Wilk wrote:
> >Hey,
> >
> >Three little patches to update the Documentation/kernel-parameters and
> >also some of the complex x86 trampoline code.
> >
> >Nothing serious, just a little cleanup.
>
> Did I miss an attachment?
No? They were part of the email thread.
>
> Rob
prev parent reply other threads:[~2013-02-26 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 20:54 [PATCH] Documentation and source code comments updates (v1) Konrad Rzeszutek Wilk
2013-02-25 20:54 ` [PATCH 1/3] xen/documentation: Mention 'earlyprintk=xen' in the documentation Konrad Rzeszutek Wilk
2013-02-25 22:13 ` [tip:x86/urgent] doc, xen: " tip-bot for Konrad Rzeszutek Wilk
2013-02-25 20:54 ` [PATCH 2/3] kernel-parameters: Document 'console=hvc<n>' Konrad Rzeszutek Wilk
2013-02-25 22:14 ` [tip:x86/urgent] doc, kernel-parameters: Document 'console=hvc<n> ' tip-bot for Konrad Rzeszutek Wilk
2013-02-25 20:54 ` [PATCH 3/3] docs: Fix incorrect comment about 64-bit code segment descriptors Konrad Rzeszutek Wilk
2013-02-25 22:15 ` [tip:x86/urgent] x86, doc: " tip-bot for Konrad Rzeszutek Wilk
2013-02-26 5:08 ` [PATCH] Documentation and source code comments updates (v1) Rob Landley
2013-02-26 16:40 ` Konrad Rzeszutek Wilk [this message]
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=20130226164034.GE15154@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=x86@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