linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: new maintainer/tree for the libata tree?
@ 2018-08-27 21:20 Stephen Rothwell
  2018-08-28  1:15 ` Jens Axboe
  0 siblings, 1 reply; 5+ messages in thread
From: Stephen Rothwell @ 2018-08-27 21:20 UTC (permalink / raw)
  To: Tejun Heo, Jens Axboe; +Cc: Linux-Next Mailing List, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 225 bytes --]

Hi Tejun, Jens,

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

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-next: new maintainer/tree for the libata tree?
  2018-08-27 21:20 linux-next: new maintainer/tree for the libata tree? Stephen Rothwell
@ 2018-08-28  1:15 ` Jens Axboe
  2018-08-28  1:28   ` Stephen Rothwell
  0 siblings, 1 reply; 5+ messages in thread
From: Jens Axboe @ 2018-08-28  1:15 UTC (permalink / raw)
  To: Stephen Rothwell, Tejun Heo
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List

On 8/27/18 3:20 PM, Stephen Rothwell wrote:
> Hi Tejun, Jens,
> 
> 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.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-next: new maintainer/tree for the libata tree?
  2018-08-28  1:15 ` Jens Axboe
@ 2018-08-28  1:28   ` Stephen Rothwell
  2018-08-28  1:30     ` Jens Axboe
  0 siblings, 1 reply; 5+ messages in thread
From: Stephen Rothwell @ 2018-08-28  1:28 UTC (permalink / raw)
  To: Jens Axboe; +Cc: Tejun Heo, Linux-Next Mailing List, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

Hi Jens,

On Mon, 27 Aug 2018 19:15:23 -0600 Jens Axboe <axboe@kernel.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?
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-next: new maintainer/tree for the libata tree?
  2018-08-28  1:28   ` Stephen Rothwell
@ 2018-08-28  1:30     ` Jens Axboe
  2018-08-28  2:43       ` Stephen Rothwell
  0 siblings, 1 reply; 5+ messages in thread
From: Jens Axboe @ 2018-08-28  1:30 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Tejun Heo, Linux-Next Mailing List, Linux Kernel Mailing List

On 8/27/18 7:28 PM, Stephen Rothwell wrote:
> Hi Jens,
> 
> On Mon, 27 Aug 2018 19:15:23 -0600 Jens Axboe <axboe@kernel.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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-next: new maintainer/tree for the libata tree?
  2018-08-28  1:30     ` Jens Axboe
@ 2018-08-28  2:43       ` Stephen Rothwell
  0 siblings, 0 replies; 5+ messages in thread
From: Stephen Rothwell @ 2018-08-28  2:43 UTC (permalink / raw)
  To: Jens Axboe; +Cc: Tejun Heo, Linux-Next Mailing List, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

Hi Jens,

On Mon, 27 Aug 2018 19:30:09 -0600 Jens Axboe <axboe@kernel.dk> wrote:
>
> On 8/27/18 7:28 PM, Stephen Rothwell wrote:
> > 
> > On Mon, 27 Aug 2018 19:15:23 -0600 Jens Axboe <axboe@kernel.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.

Done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2018-08-28  2:44 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-27 21:20 linux-next: new maintainer/tree for the libata tree? Stephen Rothwell
2018-08-28  1:15 ` Jens Axboe
2018-08-28  1:28   ` Stephen Rothwell
2018-08-28  1:30     ` Jens Axboe
2018-08-28  2:43       ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).