linux-kernel - Re: linux-next: bad commits in the nfs tree

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 4 Jun 2014 08:38:57 -0400
From:	Anna Schumaker <Anna.Schumaker@...app.com>
To:	Trond Myklebust <trond.myklebust@....uio.no>,
	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: bad commits in the nfs tree

On 06/03/2014 06:46 PM, Trond Myklebust wrote:
> On Tue, Jun 3, 2014 at 6:34 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Hi Trond,
>>
>> I noticed in the nfs tree this morning 2 commits that have been
>> cherry-picked from Linus' tree:
>>
>> cc6d854967ce    Linux 3.15-rc8
>> 2b267bb3a8e5    powerpc: Wire renameat2() syscall
>>
>> These are part of a branch that you merged from Anna Schumaker.  It
>> looks like they may have been included when Anna was trying to rebase
>> the rest of the branch onto v3.15-rc8?
>>
>> Please fix this up before asking Linus to pull your tree.
>>
> 
> Thanks Stephen! We're still ironing out the kinks in a new process for
> the NFS client maintenance, and appreciate your patience.
> 
> Anna, let's avoid the mess that is 3.15-rc8 for now. Please rebase on
> top of commit b5968725f46d (Push the file layout driver into a
> subdirectory) from my nfs-for-next branch and retag the resulting
> branch using the same commit information as earlier.
> I'll pull the new tag once you send the word that all is ready...

Sure.  I'll take care of that right away!

Anna
> 
> Thanks
>    Trond
> 

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