linux-kernel - Re: [PATCH 03/11] cpumask: update pci_bus_show

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:	Mon, 5 Jan 2009 11:44:23 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
cc:	Mike Travis <travis@....com>, Ingo Molnar <mingo@...hat.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jack Steiner <steiner@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 03/11] cpumask: update pci_bus_show_cpuaffinity to use
 new cpumask API

On Mon, 5 Jan 2009, Jesse Barnes wrote:
> 
> Can you resend these two against my linux-next branch?

Btw, Jesse, what's the schedule for merging the pci thing.

I'm currently planning on -rc1 next weekend, which gives us time to do at 
least a shortened -rc2 before people are at LCA. And the suspend/resume 
changes are some of the more "exciting" (aka scary) parts of the whole 
merge window, so I'd rather get them merged with a few days to go, rather 
than just before -rc1.

In fact, they are probably more scary than the cpumask changes, since at 
least the cpumask issues are likely to not be a big deal with any normal 
sane config (ie you really do have to enable MAXSMP to hit the stack usage 
issues). So if you end up waiting for those, I'd rather prefer to first 
merge the rest of the PCI code.

Or did the PCI late-suspend/early-resume patches go in somebody elses 
tree and I'm barking up the wrong tree entirely?

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