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 10:07:12 +0200 [thread overview]
Message-ID: <1371147.SQlum5V1iP@bentobox> (raw)
In-Reply-To: <20120619.004140.1665121006123027013.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Tuesday 19 June 2012 00:41:40 David Miller wrote:
[....]
> You must only make stable submissions for patches that have
> made their way into Linus's tree.
That is correct. These patches were meant to be sent as reply to the patch you
pulled today (that contained the initial Cc: stable@...). These were sent to
avoid the cherry-pick of feature patches necessary to merge it and still give
an idea how these versions could be fixed after the mentioned commit hit
Linus' tree.
Somebody forgot the set the In-Reply-To:.. that made these mails missing the
right context.
But we were wondering how to handle this situation anyway. The
stable_kernel_rules.txt didn't gave us the correct information (or we did not
understand them correctly) how to submit backported patches for affected
kernels. Are there some general rules that we should be aware of?
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 8:07 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 [this message]
2012-06-19 9:02 ` David Miller
2012-06-19 9:51 ` Sven Eckelmann
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=1371147.SQlum5V1iP@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