linux-kernel - Re: [stable] [PATCH v2 0/4] PCI: allocate space top-down, not bottom-up

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 24 Sep 2010 17:52:35 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Greg KH <greg@...ah.com>
Cc:	Bjorn Helgaas <bjorn.helgaas@...com>,
	Brian Bloniarz <phunge0@...mail.com>,
	Charles Butterfield <charles.butterfield@...tcentury.com>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	stable@...nel.org, Linus Torvalds <torvalds@...ux-foundation.org>,
	Stefan Becker <chemobejk@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [stable] [PATCH v2 0/4] PCI: allocate space top-down, not
 bottom-up

On Fri, 24 Sep 2010 16:40:20 -0700
Greg KH <greg@...ah.com> wrote:

> On Fri, Sep 24, 2010 at 04:41:39PM -0600, Bjorn Helgaas wrote:
> > Added cc: stable@...nel.org
> > See:
> >   https://patchwork.kernel.org/patch/189182/
> >   https://patchwork.kernel.org/patch/189232/
> >   https://patchwork.kernel.org/patch/189242/
> >   https://patchwork.kernel.org/patch/189252/
> 
> Um, why would -stable want them if they aren't in Linus's tree yet?
> Please, when they are in his tree, _AND_ have gotten a lot of testing,
> then email the git commit ids of what you want added to the stable tree
> to stable@...nel.org.
> 
> Doing it beforehand like this is a sure way to cause me a lot of work
> and the patches to be lost.

Yeah sorry.  They're queued up in a special branch atm, but will be
part of my initial 2.6.37 merge request pull.  They're not going into
2.6.36 because they're a bit too invasive for this late in the process.

I don't *think* they'll cause problems (ultimately they should make us
behave a bit more like Windows as far as resource allocation goes) so
hopefully a merge into stable sometime after the 2.6.37 merge window
closes won't be a problem, but you probably don't have a nice way of
automating that...

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/