From: Greg KH <greg@kroah.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [stable] [PATCH] avr32: Fix build failure conflicting types for 'sys_execve'
Date: Thu, 9 Dec 2010 11:13:56 -0800 [thread overview]
Message-ID: <20101209191356.GA26183@kroah.com> (raw)
In-Reply-To: <201012091942.36508.PeterHuewe@gmx.de>
On Thu, Dec 09, 2010 at 07:42:36PM +0100, Peter Hüwe wrote:
> > This is _not_ how to get stuff into the stable kernel tree, sorry.
> Sorry about that - still learning ;) - thanks for your patience.
>
> > Please read Documentation/stable_kernel_rules.txt for how to do so.
> It states: "You must note the upstream commit ID in the changelog of your
> submission." - where do I get the ID from?
That would be if the patch was in Linus's tree already. Read the next
paragraph in the document:
- To have the patch automatically included in the stable tree, add the tag
Cc: stable@kernel.org
in the sign-off area. Once the patch is merged it will be applied to
the stable tree without anything else needing to be done by the author
or subsystem maintainer.
> > Care to resend?
> Will do.
> Or should I rather drop the patch and we wait on Hans-Christian's patch(es)?
Whatever will end up in Linus's tree is the correct thing from a stable
point of view.
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-09 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 23:19 [PATCH] avr32: Fix build failure conflicting types for 'sys_execve' Peter Huewe
2010-12-09 7:54 ` Hans-Christian Egtvedt
2010-12-09 18:21 ` [stable] " Greg KH
2010-12-09 18:42 ` Peter Hüwe
2010-12-09 19:13 ` Greg KH [this message]
2010-12-09 21:15 ` [PATCH v2] " Peter Huewe
2010-12-10 10:25 ` Hans-Christian Egtvedt
2010-12-12 19:37 ` Peter Hüwe
2010-12-13 8:12 ` Hans-Christian Egtvedt
2010-12-13 17:12 ` Peter Hüwe
2010-12-13 17:27 ` Hans-Christian Egtvedt
2010-12-10 15:58 ` [PATCH] " David Howells
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=20101209191356.GA26183@kroah.com \
--to=greg@kroah.com \
--cc=PeterHuewe@gmx.de \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=hans-christian.egtvedt@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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