From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Shuah Khan <skhan@linuxfoundation•org>
Cc: Brendan Higgins <brendanhiggins@google•com>,
Mark Brown <broonie@kernel•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: Request to add linux-kselftest test branch
Date: Tue, 1 Oct 2019 07:39:13 +1000 [thread overview]
Message-ID: <20191001073913.256b5669@canb.auug.org.au> (raw)
In-Reply-To: <CAFd5g44bbh8cd=kfwLR2eFf0FRuO0d5-Mszo7P0JRLbs7e8CQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]
Hi Shuah,
On Mon, 30 Sep 2019 10:05:28 -0700 Brendan Higgins <brendanhiggins@google•com> wrote:
>
> On Thu, Sep 26, 2019 at 9:53 AM Shuah Khan <skhan@linuxfoundation•org> wrote:
> >
> > On 9/26/19 9:05 AM, Mark Brown wrote:
> > > On Wed, Sep 25, 2019 at 01:30:15PM -0600, Shuah Khan wrote:
> > >
> > >> Please add the following linux-kselftest test branch to linux-next.
> > >
> > >> https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=test
> > >
> > >> please let me know if you have questions.
> > >
> > > OK, I've added that now - I did actually merge it in by hand
> > > yesterday too. It looks like it's for kunit so I guess Brendan
> > > should be in the CC list for any issues too? Hopefully Stephen
> > > will see these mails when he gets back but it's worth checking
> > > and following up to make sure that he picks it up after he gets
> > > back on the 30th.
>
> Just following up since Mark suggested that it might be a good idea to
> do so and it doesn't look like the linux-kselftest test branch is
> currently in next-20190930.
Brendan, thanks for the reminder.
I have added this tree form today and called it kunit, I hope that is
OK.
Is this meant to be the updates for the next merge window, or fixes for
the current releasel? I ask because I notice that you also have a
"next" branch that Linus has merged for the current merge window.
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-30 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 19:30 Request to add linux-kselftest test branch Shuah Khan
2019-09-26 15:05 ` Mark Brown
2019-09-26 16:53 ` Shuah Khan
2019-09-30 17:05 ` Brendan Higgins
2019-09-30 21:39 ` Stephen Rothwell [this message]
2019-09-30 21:47 ` Brendan Higgins
2019-09-30 22:00 ` Shuah Khan
2019-09-30 22:02 ` Stephen Rothwell
2019-09-30 22:09 ` Shuah Khan
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=20191001073913.256b5669@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brendanhiggins@google$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=skhan@linuxfoundation$(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