linux-kernel - Re: [GIT pull] irq fixes for .39.rc

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:	Wed, 30 Mar 2011 18:46:09 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT pull] irq fixes for .39.rc

On Wed, 30 Mar 2011, Thomas Gleixner wrote:
> On Wed, 30 Mar 2011, Linus Torvalds wrote:
> > 
> > which just makes me go "Somebody is really really confused".
> > 
> > The whole thing may mean that both handler_data and chip_data contains
> > the right thing, but it still makes me go "WTF?".
> > 
> > Which way should I resolve it?
> 
> get_irq_desc_data() maps to irq_desc_get_handler_data() so Richards
> resolution is correct even if the other might work as well.

Older code which was not using any accessors has:

      desc->handler_data

But yeah, the init stuff is confusing as hell.

Thanks,

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