From: Mark Brown <broonie@kernel•org>
To: Shuah Khan <skhan@linuxfoundation•org>,
Brendan Higgins <brendanhiggins@google•com>
Cc: linux-next@vger•kernel.org, Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: Request to add linux-kselftest test branch
Date: Thu, 26 Sep 2019 08:05:38 -0700 [thread overview]
Message-ID: <20190926150538.GS2036@sirena.org.uk> (raw)
In-Reply-To: <8b9795d2-a384-dec8-076c-5b9d5c524eba@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
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.
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-26 15:05 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 [this message]
2019-09-26 16:53 ` Shuah Khan
2019-09-30 17:05 ` Brendan Higgins
2019-09-30 21:39 ` Stephen Rothwell
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=20190926150538.GS2036@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=brendanhiggins@google$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--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