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]
Message-ID: <1426525919.23897.11.camel@perches.com>
Date:	Mon, 16 Mar 2015 10:11:59 -0700
From:	Joe Perches <joe@...ches.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Jes Sorensen <Jes.Sorensen@...hat.com>,
	"M. Vefa Bicakci" <m.v.b@...box.com>,
	Matthias Beyer <mail@...ermatthias.de>,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	Larry.Finger@...inger.net
Subject: Re: [PATCH v2 00/16] checkpatch clean-up of rtl8723au's
 rtw_security.c

On Mon, 2015-03-16 at 18:07 +0100, Greg KH wrote:
> On Mon, Mar 16, 2015 at 09:55:27AM -0700, Joe Perches wrote:
> > On Mon, 2015-03-16 at 12:01 -0400, Jes Sorensen wrote:
> > > For staging patches, you should always post patches against the
> > > staging-next tree. Please rebase them and repost them.
> > Greg is now preferring patches against his
> > staging-testing branch
> staging-testing only lasts a day or so before it turns into
> staging-next, so you are usually safe with using staging-next.

Yeah but that usually is nothing but painful for
those that are unfortunate enough to hit it.


--
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