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] [day] [month] [year] [list]
Date:	Tue, 24 Nov 2009 06:35:35 -0800
From:	Greg KH <greg@...ah.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	monstr@...str.eu, chrisw@...s-sol.org,
	linux-kernel@...r.kernel.org, grant.likely@...retlab.ca,
	alonz@...cretix.com, linux-serial@...r.kernel.org,
	stable@...nel.org, john.williams@...alogix.com
Subject: Re: [stable] [PATCH] serial: 8250: Add ns16550a to OF compatible
	list

On Tue, Nov 24, 2009 at 09:53:52AM +0000, Arnd Bergmann wrote:
> On Tuesday 24 November 2009 09:21:42 monstr@...str.eu wrote:
> > From: Michal Simek <monstr@...str.eu>
> > 
> > Signed-off-by: Michal Simek <monstr@...str.eu>
> 
> I was holding off on that patch to make sure the discussion had ended,
> but this part certainly looks good.
> 
> Some points on form though:
> 
> * The patch is missing a changelog, which is always required, but especially
> important if you're changing code that you want in -stable!
> 
> * You did not cc me. Ok, I just noticed I'm missing an entry in the MAINTAINERS
> file, but scripts/get_maintainer.pl would have given you a good indication of
> who feels responsible. You also didn't cc Alon, who submitted a similar patch
> [1] just days ago, which I assume prompted you to send this. If you didn't see
> his patch, nevermind.
> 
> * Patches go into mainline first, then into stable [2]. Asking for inclusion into
> -stable for a patch that is still being discussed for inclusion in -next is
> the wrong order, no matter how obvious and trivial the patch is.

The easiest way to do this is to add:
	cc: stable <stable@...nel.org>
to the signed-off-by area of the patch.  Then, when it goes into Linus's
tree the stable developers will be automatically notified of it and suck
it into their tree as well, no additional work needs to be done by you
at all.

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