linux-kernel - Re: [patch 00/19] gpio: Interrupt cleanups and API change preparation

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: <CACRpkdZqGfB-5e+gt8qk+m+iXnO8+S7K_-qQbL+nvHQaxD36BQ@mail.gmail.com>
Date:	Thu, 16 Jul 2015 15:55:40 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Alexandre Courbot <gnurou@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Jiang Liu <jiang.liu@...ux.intel.com>
Subject: Re: [patch 00/19] gpio: Interrupt cleanups and API change preparation

On Mon, Jul 13, 2015 at 10:41 PM, Thomas Gleixner <tglx@...utronix.de> wrote:

> The following patch series contains the following changes:
>
>     - Consolidation of chained interrupt handler setup/removal
>
>     - Switch to functions which avoid a redundant interrupt
>       descriptor lookup
>
>     - Preparation of interrupt flow handlers for the 'irq' argument
>       removal
>
> The series has no dependencies and is also available as a git branch
> for your convenience:
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/gpio

Hmm.....

git pull git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/gpio
fatal: Couldn't find remote ref irq/gpio

Same with pinctrl, did you push it?

Or am I a shitty git operator ... don't rule that out :/

Yours,
Linus Walleij
--
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/