From: Akira Hayakawa <ruby.wktk@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [Question] How to make a patch?
Date: Sat, 10 Aug 2013 08:47:11 +0900 [thread overview]
Message-ID: <52057F7F.7090406@gmail.com> (raw)
In-Reply-To: <20130809232226.GA4493@agk-dp.fab.redhat.com>
On 8/10/13 8:22 AM, Alasdair G Kergon wrote:
> At this stage, create a patch based against a released -rc kernel
> from Linus.
>
> If you use the linux-dm tree, then you can pick the tag v3.11-rc3,
> for example, which is the last time we updated.
Thanks for your response.
And I have a further question.
Do you mean
making a patch against rc4 in linux-next is not preferred?
I think if doing so,
the patch will be unable to apply to linux-dm
which I believe one going to be suggested to Linus.
I think I am going to make my patch against
v3.11-rc3 in linux-dm.
But, patching on kernel as fresh as possible
would make sense more.
next prev parent reply other threads:[~2013-08-09 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 23:12 [Question] How to make a patch? Akira Hayakawa
2013-08-09 23:22 ` Alasdair G Kergon
2013-08-09 23:47 ` Akira Hayakawa [this message]
2013-08-10 0:07 ` Alasdair G Kergon
2013-08-10 0:43 ` Akira Hayakawa
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=52057F7F.7090406@gmail.com \
--to=ruby.wktk@gmail.com \
--cc=dm-devel@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).