From: "H. Peter Anvin" <hpa@zytor.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Christoph Hellwig <hch@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use __kernel_long_t/__kernel_ulong_t in <linux/resource.h>
Date: Thu, 26 Dec 2013 11:13:37 -0800 [thread overview]
Message-ID: <52BC7FE1.6070508@zytor.com> (raw)
In-Reply-To: <CAMe9rOqx1HDT_rtiz2R0Cz5iAp0AFXhjw6RpTkjgFT_DDDWfVA@mail.gmail.com>
On 12/26/2013 05:52 AM, H.J. Lu wrote:
>>
>> a) please send all your related patches as a series
>
> My patches are independent of each other. They can
> be applied in order.
>
Sure, but the convention in the Linux community is to send them all as a
"series" using git send-email, preferably with a introductory cover
letter as the "0/N patch" so they arrive in a single thread and can be
reviewed together. Otherwise bits tend to get lost in the enormous
flood of email that is LKML.
-hpa
next prev parent reply other threads:[~2013-12-26 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 14:54 [PATCH] Use __kernel_long_t/__kernel_ulong_t in <linux/resource.h> H.J. Lu
2013-12-26 10:03 ` Christoph Hellwig
2013-12-26 13:52 ` H.J. Lu
2013-12-26 13:54 ` H.J. Lu
2013-12-26 17:58 ` H. Peter Anvin
2013-12-26 18:08 ` H.J. Lu
2013-12-26 19:13 ` H. Peter Anvin [this message]
2013-12-26 15:36 ` H.J. Lu
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=52BC7FE1.6070508@zytor.com \
--to=hpa@zytor.com \
--cc=hch@infradead.org \
--cc=hjl.tools@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox