* bcache request for pull
@ 2017-10-13 20:54 Michael Lyle
2017-10-13 20:56 ` Jens Axboe
0 siblings, 1 reply; 2+ messages in thread
From: Michael Lyle @ 2017-10-13 20:54 UTC (permalink / raw)
To: linux-next; +Cc: Jens Axboe, linux-bcache
Hi--
I'm stepping up as new maintainer of bcache and have put together a git
repository of patches targeting the next merge window. Can it please be
added to the set of repositories that linux-next pulls from?
it's https://github.com/mlyle/linux.git bcache-for-next
Thanks,
Mike
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: bcache request for pull
2017-10-13 20:54 bcache request for pull Michael Lyle
@ 2017-10-13 20:56 ` Jens Axboe
0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2017-10-13 20:56 UTC (permalink / raw)
To: Michael Lyle, linux-next; +Cc: linux-bcache
On 10/13/2017 02:54 PM, Michael Lyle wrote:
> Hi--
>
> I'm stepping up as new maintainer of bcache and have put together a git
> repository of patches targeting the next merge window. Can it please be
> added to the set of repositories that linux-next pulls from?
>
> it's https://github.com/mlyle/linux.git bcache-for-next
First of all, you need to send the patches out for review. When they are
properly reviewed, they can be added to the block tree for inclusion
in the next merge window. Once they are added there, they will show
up in linux-next automatically.
--
Jens Axboe
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-10-13 20:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-13 20:54 bcache request for pull Michael Lyle
2017-10-13 20:56 ` Jens Axboe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox