From: Andy Shevchenko <andy@kernel.org>
To: David Gow <davidgow@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Rae Moar <rmoar@google.com>, Kees Cook <kees@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Brendan Higgins <brendan.higgins@linux.dev>
Subject: Re: [PATCH v2 0/6] [PATCH 0/6] KUnit test moves / renames
Date: Mon, 2 Dec 2024 18:01:34 +0200 [thread overview]
Message-ID: <Z03Z3k3OdK4VHEh5@smile.fi.intel.com> (raw)
In-Reply-To: <20241202075545.3648096-1-davidgow@google.com>
On Mon, Dec 02, 2024 at 03:55:37PM +0800, David Gow wrote:
> As discussed in [1], the KUnit test naming scheme has changed to avoid
> name conflicts (and tab-completion woes) with the files being tested.
> These renames and moves have caused a nasty set of merge conflicts, so
> this series collates and rebases them all on top of v6.13-rc1, to be
> applied minimising any further conflicts. [2,3]
>
> Thanks to everyone whose patches appear here, and everyone who reviewed
> on the original series. I hope I didn't break them too much during the
> rebase!
>
> Link: https://lore.kernel.org/lkml/20240720165441.it.320-kees@kernel.org/ [1]
> Link: https://lore.kernel.org/lkml/CABVgOSmbSzcGUi=E4piSojh3A4_0GjE0fAYbqKjtYGbE9beYRQ@mail.gmail.com/ [2]
> Link: https://lore.kernel.org/linux-kselftest/CABVgOSkhD6=5K72oL_n35CUeMhbsiQjZ6ds+EuQmJggBtVTFVg@mail.gmail.com/ [3]
>
> Bruno Sobreira França (1):
> lib/math: Add int_log test suite
>
> Diego Vieira (1):
> lib/tests/kfifo_kunit.c: add tests for the kfifo structure
>
> Gabriela Bittencourt (2):
> unicode: kunit: refactor selftest to kunit tests
> unicode: kunit: change tests filename and path
>
> Kees Cook (1):
> lib: Move KUnit tests into tests/ subdirectory
>
> Luis Felipe Hernandez (1):
> lib: math: Move kunit tests into tests/ subdir
Can we deduplicate test/kunit in the file names please?
See df7f9acd8646 ("platform/x86: intel: Add 'intel' prefix to the modules
automatically") for the details how to achieve that in non-verbose way.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-12-02 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 7:55 [PATCH v2 0/6] [PATCH 0/6] KUnit test moves / renames David Gow
2024-12-02 7:55 ` [PATCH v2 1/6] lib: math: Move kunit tests into tests/ subdir David Gow
2024-12-02 7:55 ` [PATCH v2 2/6] lib/math: Add int_log test suite David Gow
2024-12-02 7:55 ` [PATCH v2 3/6] lib: Move KUnit tests into tests/ subdirectory David Gow
2024-12-02 7:55 ` [PATCH v2 4/6] lib/tests/kfifo_kunit.c: add tests for the kfifo structure David Gow
2024-12-02 7:55 ` [PATCH v2 5/6] unicode: kunit: refactor selftest to kunit tests David Gow
2024-12-02 7:55 ` [PATCH v2 6/6] unicode: kunit: change tests filename and path David Gow
2024-12-02 16:01 ` Andy Shevchenko [this message]
2024-12-02 23:29 ` [PATCH v2 0/6] [PATCH 0/6] KUnit test moves / renames Rae Moar
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=Z03Z3k3OdK4VHEh5@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=geert@linux-m68k.org \
--cc=kees@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmoar@google.com \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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