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:	Fri, 10 Sep 2010 20:14:58 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Andres Salomon <dilinger@...ued.net>,
	devicetree-discuss@...ts.ozlabs.org, x86@...nel.org,
	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	Mitch Bradley <wmb@...top.org>, linux-kernel@...r.kernel.org,
	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>
Subject: Re: [PATCH 2/2] x86: of: define irq functions to allow drivers/of/*
 to build on x86


* Grant Likely <grant.likely@...retlab.ca> wrote:

> On Fri, Sep 10, 2010 at 06:01:51AM -0700, Andres Salomon wrote:
> > 
> >  - Define a stub irq_create_of_mapping for x86 as a stop-gap solution until
> >    drivers/of/irq is further along.
> >  - Define irq_dispose_mapping for x86 to appease of_i2c.c
> > 
> > Signed-off-by: Andres Salomon <dilinger@...ued.net>
> 
> Applied to my test-devicetree branch.  I'll need an ack from the x86 
> maintainers before I put it into my -next branch.

The purpose of the patch is not clear to me. What does it do and why? 
The changelog says it's a stopgap measure - what exactly is the long 
term plan and how long will it take?

Thanks,

	Ingo
--
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