linux-kernel - Re: [PATCH v2] of/irq: lookup 'interrupts-extended' property first

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] [day] [month] [year] [list]

Date:	Fri, 15 Aug 2014 13:51:28 +0100
From:	Grant Likely <grant.likely@...aro.org>
To:	Brian Norris <computersforpeace@...il.com>,
	Florian Fainelli <f.fainelli@...il.com>
Cc:	devicetree@...r.kernel.org, robh+dt@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] of/irq: lookup 'interrupts-extended' property first

On Wed, 6 Aug 2014 13:15:00 -0700, Brian Norris <computersforpeace@...il.com> wrote:
> On Wed, Aug 06, 2014 at 01:02:27PM -0700, Florian Fainelli wrote:
> > In case the Device Tree blob passed by the boot agent supplies both an
> > 'interrupts-extended' and an 'interrupts' property in order to allow for
> > older kernels to be usable, prefer the new-style 'interrupts-extended'
> > property which conveys a lot more information.
> > 
> > This allows us to have bootloaders willingly maintaining backwards
> > compatibility with older kernels without entirely deprecating the
> > 'interrupts' property.
> > 
> > Update the bindings documentation to describe a situation where both the
> > 'interrupts-extended' and the 'interrupts' property are present, and
> > which one takes precedence over the other.
> > 
> > Acked-by: Rob Herring <robh@...nel.org>
> > Signed-off-by: Brian Norris <computersforpeace@...il.com>
> > Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
> 
> Might we add this?
> 
> Cc: <stable@...r.kernel.org> # 3.13+
> 
> Brian

Applied, thanks.

g.

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