public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Brendan Higgins <brendanhiggins@google•com>
Cc: Shuah Khan <skhan@linuxfoundation•org>,
	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 08:02:00 +1000	[thread overview]
Message-ID: <20191001080200.0e9a5a31@canb.auug.org.au> (raw)
In-Reply-To: <CAFd5g47Aq4kWeU2NU2ogSAcf-Z5XNEzk90Fjh8z_s2xv2Vs+Ng@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

Hi Brendan,

On Mon, 30 Sep 2019 14:47:34 -0700 Brendan Higgins <brendanhiggins@google•com> wrote:
>
> Linus had a minor complaint with the KUnit patches, so we had to fix
> them and pull them out into a separate branch. We didn't get enough
> coverage on the updated patches in time for rc1, so we are hoping we
> can get away with sending them in as part of rc2; if that doesn't work
> then it will be for the next merge window.

Ah, OK.  And I just noticed that the "next" branch is actually my
"kselfest" tree ...

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-09-30 22:02 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
2019-09-30 21:47         ` Brendan Higgins
2019-09-30 22:00           ` Shuah Khan
2019-09-30 22:02           ` Stephen Rothwell [this message]
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=20191001080200.0e9a5a31@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