linux-kernel - Re: [GIT PULL] GPIO bulk changes for kernel v4.6

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: <56EBCCDC.8070405@nvidia.com>
Date:	Fri, 18 Mar 2016 15:09:40 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Linus Walleij <linus.walleij@...aro.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [GIT PULL] GPIO bulk changes for kernel v4.6


On Friday 18 March 2016 02:31 PM, Linus Walleij wrote:
> On Fri, Mar 18, 2016 at 7:07 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>> On Thu, Mar 17, 2016 at 1:59 AM, Linus Walleij <linus.walleij@...aro.org> wrote:
>>> The end result should be clean but the history is a bit messy.
>> Gaah. I took the tree, but I didn't realize just *how* messy it was. I
>> doubt you did either.
> Certainly not. I wasn't even aware that things could be screwed up so
> much and still look OK on the surface. I'll certainly be more cautious
> about pulling branches in the future.
>

Apologizing for the trouble created by me. I understand from other mail 
that It seems I have misguided by the step mentioned in github document 
and so created the issue. I will not use github as mentioned by Linus T.