From: Sven Eckelmann <sven@narfation.org>
To: David Miller <davem@davemloft.net>
Cc: b.a.t.m.a.n@lists.open-mesh.org, stable@vger.kernel.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: fix skb->data assignment
Date: Tue, 19 Jun 2012 11:51:50 +0200 [thread overview]
Message-ID: <2579267.utmNKQaN8a@bentobox> (raw)
In-Reply-To: <20120619.020227.393422018169766346.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On Tuesday 19 June 2012 02:02:27 David Miller wrote:
[....]
> Patches you want to end up in -stable should be submitted for 'net'
> not 'net-next'.
>
> There is no other valid submission scheme.
I know that. This is also completely right and not contested by me. I did not
submit/create the pull request and don't want to talk about that part too
much. At least I am not very good in speaking for other people and don't want
to create more hiccups than I already caused :)
The part that was more interesting for me is the backporting (+ submission of
these patches) or annotation to which kernel that patch should be backported.
The stable_kernel_rules.txt gives a nice overview about how to say which other
patches should be cherry-picked to get this fix applied. But we could also
have the problem with kernel version that are not obvious (since the patch
doesn't apply directly on that version) and a backported patch is a better
choice than cherry-picking many other things.
Is it correct as Antonio did it (submitting more than one patch, but with a
special "# 3.x" for each one after the Cc: )?
I don't want a big discussion. Just a small hint how it is preferred (maybe
nothing should be done and the stable committee will guess it.. for example
the commit id that introduced the problem was missing, but could be used to
find the affected kernels quite easily).
Thanks,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-19 9:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 7:20 [B.A.T.M.A.N.] [PATCH] batman-adv: fix skb->data assignment Antonio Quartulli
2012-06-19 7:41 ` David Miller
2012-06-19 8:07 ` Sven Eckelmann
2012-06-19 9:02 ` David Miller
2012-06-19 9:51 ` Sven Eckelmann [this message]
2012-06-19 12:10 ` Ben Hutchings
2012-06-19 12:41 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2012-06-19 7:23 Antonio Quartulli
2012-06-14 20:21 Antonio Quartulli
2012-06-15 11:45 ` Sven Eckelmann
2012-06-15 11:50 ` Antonio Quartulli
2012-06-15 19:09 ` Marek Lindner
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=2579267.utmNKQaN8a@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=stable@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