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
| ||
|
Date: Fri, 10 Oct 2008 15:09:38 -0700 From: Greg KH <greg@...ah.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: linux-kernel@...r.kernel.org, Stefan Bader <stefan.bader@...onical.com>, stable@...nel.org, "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] x86: Reserve FIRST_DEVICE_VECTOR in used_vectors bitmap On Fri, Oct 10, 2008 at 10:49:07PM +0100, Alan Cox wrote: > > > And more importantly dev->irq == 0 or IRQ == 0 to anything but arch > > > internal code means "no interrupt line". > > > > I thought we had changed that a while ago, as some arches had 0 as a > > valid irq line. > > No .. Linus decreed (and I think sensibly myself that IRQ = 0 meant no > IRQ assigned).. the argument being that in C you naturally write stuff > like > > if (!dev->irq) Ok, I was confused, thanks. > I can dig up the reference URLS to the list mails if you want Nah, I trust you :) 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