From: Greg KH <greg@kroah.com>
To: Peter Huewe <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>,
stable@kernel.org
Subject: Re: [stable] [PATCH] avr32: Fix build failure conflicting types for 'sys_execve'
Date: Thu, 9 Dec 2010 10:21:32 -0800 [thread overview]
Message-ID: <20101209182132.GB24175@kroah.com> (raw)
In-Reply-To: <1291850373-6955-1-git-send-email-peterhuewe@gmx.de>
On Thu, Dec 09, 2010 at 12:19:33AM +0100, Peter Huewe wrote:
> This patch fixes a build failure[1] for the avr32 architecture which seems
> to be introduced by commit d7627467b7a8
> "Make do_execve() take a const filename pointer"
>
> The commit changes the definition in arch/avr32/kernel/process.c but
> forgot to change it here.
>
> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
> ---
> This build failure exists in linus' tree - added stable@kernel.org to the cc list
This is _not_ how to get stuff into the stable kernel tree, sorry.
Please read Documentation/stable_kernel_rules.txt for how to do so.
Hint, put:
Cc: stable <stable@kernel.org.
in the signed-off-by: area of your patch and then you will automatically
get the patch applied to the stable trees when it goes to Linus.
Otherwise I have to dig through commit logs and hope to find it, which
wastes lots of time when it's not there yet.
Care to resend?
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-09 18: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 ` Greg KH [this message]
2010-12-09 18:42 ` [stable] " Peter Hüwe
2010-12-09 19:13 ` Greg KH
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=20101209182132.GB24175@kroah.com \
--to=greg@kroah.com \
--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=peterhuewe@gmx.de \
--cc=stable@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 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.