From: Jens Axboe <axboe@kernel•dk>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Tejun Heo <tj@kernel•org>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: new maintainer/tree for the libata tree?
Date: Mon, 27 Aug 2018 19:15:23 -0600 [thread overview]
Message-ID: <27ef8afc-c490-5984-5a18-1ee5ce51d556@kernel.dk> (raw)
In-Reply-To: <20180828071944.02b13db4@canb.auug.org.au>
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
next prev parent reply other threads:[~2018-08-28 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 21:20 linux-next: new maintainer/tree for the libata tree? Stephen Rothwell
2018-08-28 1:15 ` Jens Axboe [this message]
2018-08-28 1:28 ` Stephen Rothwell
2018-08-28 1:30 ` Jens Axboe
2018-08-28 2:43 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27ef8afc-c490-5984-5a18-1ee5ce51d556@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox