From: lists@kaiser.cx (Martin Kaiser)
To: kernelnewbies@lists.kernelnewbies.org
Subject: submitting a patch for a stable tree
Date: Sun, 17 Dec 2017 20:24:36 +0100 [thread overview]
Message-ID: <20171217192436.GA1621@botnar.kaiser.cx> (raw)
Dear all,
I tried to submit a patch for 4.14 that was already accepted upstream
and is in linux-next and the 4.15-rcs.
To understand how this should be done, I looked at
https://www.kernel.org/doc/html/v4.14/process/stable-kernel-rules.html
and tried to follow Option 2. It looks like I didn't get it right.
I started with a tree that contains the patch and ran
git format-patch -1 <commit id>
and then
git send-email --to stable at verg.kernel.org \
--cc <the original maintainer and reviewers> \
--annotate <patch file>
I added the upstream commit id above the original commit message and a
tag line
Cc: <stable@vger.kernel.org> # 4.14.x
to the patch and sent it out.
Is there anything that's wrong or missing? Is there a mailing list
archive for stable at vger.kernel.org where I can have a look at correct
submissions and check that my submission made it to the list?
Thanks for your help,
Martin
next reply other threads:[~2017-12-17 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 19:24 Martin Kaiser [this message]
2017-12-17 20:23 ` submitting a patch for a stable tree Greg KH
2017-12-18 9:38 ` Greg KH
2017-12-18 13:04 ` Martin Kaiser
2017-12-18 12:54 ` Martin Kaiser
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=20171217192436.GA1621@botnar.kaiser.cx \
--to=lists@kaiser.cx \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.