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.DEB.2.11.1509081603360.3854@nanos>
Date:	Tue, 8 Sep 2015 16:10:28 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Linus Walleij <linus.walleij@...aro.org>
cc:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Jiang Liu <jiang.liu@...ux.intel.com>
Subject: Re: [patch 15/22] pinctrl: Use irq_desc_get_xxx() to avoid redundant
 lookup of irq_desc

On Tue, 8 Sep 2015, Linus Walleij wrote:
> On Mon, Aug 31, 2015 at 11:28 PM, Paul Gortmaker
> <paul.gortmaker@...driver.com> wrote:
> > On Mon, Jul 13, 2015 at 4:47 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
> >> From: Jiang Liu <jiang.liu@...ux.intel.com>
> >>
> >> Use irq_desc_get_xxx() to avoid redundant lookup of irq_desc while we
> >> already have a pointer to corresponding irq_desc.
> >
> > Hi Linus,
> >
> > It seems that linux-next has this copy of the patch as 5663bb27dec1, which
> > has a stray irq_desc_get_irq_chip in s3c24xx ; (2nd instance of "irq" is
> > bogus looking.)   I first assumed it was from tglx since it did not have any
> > additional SOB lines, but on further investigation I traced it back to sfr's
> > merge of pinctrl/for-next.
> 
> Hm, saw this a bit late I guess.
> 
> Torvalds has merged my trees, is there a problem in mainline
> that need to be addressed or did this fix itself?

No, it's buggered in Linus tree as well.

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