linux-kernel - Re: linux-next: new maintainer/tree for the libata 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <0ee8b9e0-1576-c8c1-ed22-dd76a8d378ba@kernel.dk>
Date:   Mon, 27 Aug 2018 19:30:09 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Tejun Heo <tj@...nel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: new maintainer/tree for the libata tree?

On 8/27/18 7:28 PM, Stephen Rothwell wrote:
> Hi Jens,
> 
> On Mon, 27 Aug 2018 19:15:23 -0600 Jens Axboe <axboe@...nel.dk> wrote:
>>
>> On 8/27/18 3:20 PM, Stephen Rothwell wrote:
>>>
>>> I noticed the maintaership change - so what shuld I sues for linux-next,
>>> now?
>>>
>>> I currently have
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git#for-next  
>>
>> I'll merge into my for-next branch on the block tree, I'm don't plan on
>> doing separate trees for this, just separate branches. And everything I
>> queue up for the next version will end up in my for-next branch.
> 
> So I'll just drop the libata tree from linux-next, then?

Yeah, that should be all that's needed.

-- 
Jens Axboe