From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bart Van Assche <bart.vanassche@gmail•com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi•org>,
linux-next@vger•kernel.org, target-devel@vger•kernel.org
Subject: Re: Please add bvanassche/linux.git/for-next to linux-next
Date: Mon, 19 Dec 2016 09:05:41 +1100 [thread overview]
Message-ID: <20161219090529.25e15aa8@canb.auug.org.au> (raw)
In-Reply-To: <8952a919-1d55-301d-8b50-b3177713acc5@acm.org>
Hi Bart,
On Sun, 18 Dec 2016 11:51:28 +0100 Bart Van Assche <bart.vanassche@gmail•com> wrote:
>
> Nicholas Bellinger, the official SCSI target maintainer, stopped sending
> pull requests for the SCSI target subsystem (drivers/target) to Linus
> and I would like to take over. Nic has been CC-ed for the e-mail
> conversation below.
[Nicholas, should I remove the the target-updates and/or target-merge
trees from linux-next?]
> I have pushed out the patches I would like to send to Linus during the
> v4.10 merge window to
> kernel.org:/pub/scm/linux/kernel/git/bvanassche/linux.git/for-next.
I assume you meant
git://git.kernel.org/pub/scm/linux/kernel/git/bvanassche/linux.git#for-next
> Would it be possible to add that branch to the linux-next test system?
Added from today. For now it is called target-bva, but I will change
that when Nicholas replies to the above question.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@canb•auug.org.au
parent reply other threads:[~2016-12-18 22:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8952a919-1d55-301d-8b50-b3177713acc5@acm.org>]
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=20161219090529.25e15aa8@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bart.vanassche@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nab@linux-iscsi$(echo .)org \
--cc=target-devel@vger$(echo .)kernel.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