linux-kernel - Re: [PATCH] powerpc: fixup after irq changes

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: <17703.40127.482493.417591@cargo.ozlabs.ibm.com>
Date:	Sat, 7 Oct 2006 22:25:35 +1000
From:	Paul Mackerras <paulus@...ba.org>
To:	Olaf Hering <olaf@...fle.de>, Linus Torvalds <torvalds@...l.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	David Howells <dhowells@...hat.com>,
	Andrew Morton <akpm@...l.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, Dmitry Torokhov <dtor@...l.ru>,
	Greg KH <greg@...ah.com>, David Brownell <david-b@...bell.net>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: [PATCH] powerpc: fixup after irq changes

I wrote:

> You also removed the regs argument from the get_irq functions.  That
> is a separate unrelated change, which I would want to think about for
> a bit, because at least at one stage I had a use for that parameter.

I remembered the use I had for it - for interrupt controllers that
want to save away an old cpu priority value or similar.  The ones that
need to do that (xics and cell) either don't do it (xics :) or use a
per-cpu array (cell).  Also, we call get_irq from an interrupt handler
for cascaded interrupts in some cases.  So I have applied your patch
and fixed the rejects.

Thanks,
Paul.
-
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/