linux-kernel - Re: linux-next: Tree for Jun 27 (pinctrl && !CONFIG

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:	Tue, 5 Jul 2016 08:48:53 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Randy Dunlap <rdunlap@...radead.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: linux-next: Tree for Jun 27 (pinctrl && !CONFIG_OF)

On Mon, Jul 4, 2016 at 6:12 PM, Randy Dunlap <rdunlap@...radead.org> wrote:

>> I merged it I think, Alex made a long series enabling compile
>> testing and I started to cherry-pick the first commits to let
>> them trickle in.
>
> I guess that when you do a git pull of a series of patches, you
> sign the pull commit but not each patch in the series?
> That could explain it.

I think I cherry-picked it actually. But yeah.

> I agree with Arnd that this particular commit should be reverted
> (1e4a80640338924b9f9fd7a121ac31d08134410a).

I've reverted it for fixes.

Yours,
Linus Walleij