From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bart Van Assche <bart.vanassche@sandisk•com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi•org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the target-bva tree with the target-updates tree
Date: Fri, 2 Jun 2017 09:28:46 +1000 [thread overview]
Message-ID: <20170602092846.2ebba861@canb.auug.org.au> (raw)
In-Reply-To: <aff8f6fa-89b4-3dee-2c3f-68eae613fbba@sandisk.com>
Hi Bart,
On Thu, 1 Jun 2017 14:14:06 -0700 Bart Van Assche <bart.vanassche@sandisk•com> wrote:
>
> On 05/31/17 22:04, Nicholas A. Bellinger wrote:
> > Go ahead and get list review on drivers/target/ changes before pushing
> > them into linux-next, please.
> >
> > Btw, I don't care if you queue up one's that do have at least two
> > Reviewed-bys into your tree, but everything that doesn't have
> > Reviewed-bys or Acked-by should not be going into linux-next.
>
> It is not your job to rewrite the rules for linux-next. I'm following
> the guidelines I received from Stephen in December 2016. You were copied
> on the e-mail with guidelines Stephen sent to me. See also
> https://www.spinics.net/lists/linux-next/msg38488.html.
>
> Stephen, if anything would have changed in the meantime that I'm not
> aware of please let me know.
This is what I tell everyone:
"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."
Which is just what was in that message you pointed to. Note the
"reviewed by you (or another maintainer of your subsystem tree)". This
is more meant for the top level maintainers, but implies that the
patches have been reviewed, tested and are as ready as possible for
merging into the next level up tree.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-06-01 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 4:10 linux-next: manual merge of the target-bva tree with the target-updates tree Stephen Rothwell
2017-06-01 4:27 ` Nicholas A. Bellinger
2017-06-01 5:05 ` Bart Van Assche
2017-06-01 5:15 ` Nicholas A. Bellinger
2017-06-01 4:59 ` Bart Van Assche
2017-06-01 5:04 ` Nicholas A. Bellinger
2017-06-01 21:14 ` Bart Van Assche
2017-06-01 23:28 ` Stephen Rothwell [this message]
2017-06-02 3:58 ` Nicholas A. Bellinger
-- strict thread matches above, loose matches on Subject: below --
2017-06-02 4:05 Stephen Rothwell
2017-06-02 4:11 ` Stephen Rothwell
2017-02-20 2:51 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=20170602092846.2ebba861@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bart.vanassche@sandisk$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nab@linux-iscsi$(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