lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 9 Dec 2010 11:13:56 -0800
From:	Greg KH <greg@...ah.com>
To:	Peter Hüwe <PeterHuewe@....de>
Cc:	Hans-Christian Egtvedt <hans-christian.egtvedt@...el.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	David Howells <dhowells@...hat.com>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [stable] [PATCH] avr32: Fix build failure conflicting types
 for 'sys_execve'

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@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ