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: <alpine.LFD.1.10.0804221651400.2779@woody.linux-foundation.org>
Date:	Tue, 22 Apr 2008 16:52:44 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jeff Garzik <jeff@...zik.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, rmk@....linux.org.uk
Subject: Re: [git patch] free_irq() fixes



On Tue, 22 Apr 2008, Jeff Garzik wrote:
> [...]
> > Since the #irq-remove project involves removal of the 'irq' argument
> > from interrupt handlers (unused 99.8% of the time),
> [...]
> 
> After going over every irq handler (read: almost every driver in the kernel,
> plus arch code), my #irq-remove branch has confirmed what my gut already knew
> -- the 'irq' argument is completely unused for almost every driver.  So I was
> taking that line of thought as far as it went.

Ok, that's just not going to happen.

What's the upside? Really?

I can tell you the downsides:
 - tons of huge patches with ugly churn
 - total disaster when it comes to any drivers that are maintained over 
   multiple versions and/or out-of-tree like the DRI stuff

so those upsides had better be really big.

		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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ