From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Gow <davidgow@google•com>
Cc: Shuah Khan <skhan@linuxfoundation•org>,
Brendan Higgins <brendanhiggins@google•com>,
Arnd Bergmann <arnd@arndb•de>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the kunit-next tree with the kunit-fixes tree
Date: Wed, 1 Feb 2023 16:37:12 +1100 [thread overview]
Message-ID: <20230201163712.4336d3a1@canb.auug.org.au> (raw)
In-Reply-To: <CABVgOS=SRvs6fcNzbfDnR=p91TwdKiX5NBeLSCx3FPMCEbzU5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hi David,
On Wed, 1 Feb 2023 12:31:49 +0800 David Gow <davidgow@google•com> wrote:
>
> As you noted, the "hooks" patch is meant to supersede "kunit: Export
> kunit_running()", which is really meant as a fix for older kernels
> which won't get the "hooks" patch.
>
> I imagine we'll rebase this once the fixes go upstream.
Or just merge what you ask Linus to merge, for a minimal change.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-01 5:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 2:49 linux-next: manual merge of the kunit-next tree with the kunit-fixes tree Stephen Rothwell
2023-02-01 4:31 ` David Gow
2023-02-01 5:37 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-03 14:00 Mark Brown
2026-03-04 9:16 ` David Gow
2026-03-31 19:36 ` Shuah Khan
2026-04-01 10:33 ` Mark Brown
2022-11-01 3:31 Stephen Rothwell
2021-10-08 4:29 Stephen Rothwell
2021-10-08 16:31 ` Shuah Khan
2021-10-08 20:03 ` Brendan Higgins
2021-10-08 20:48 ` Daniel Latypov
2021-10-19 21:26 ` Shuah Khan
2021-10-19 21:40 ` Daniel Latypov
2021-10-19 22:20 ` 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=20230201163712.4336d3a1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=brendanhiggins@google$(echo .)com \
--cc=davidgow@google$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.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