linux-ext4 - Re: (subset) [PATCH v2 0/6] kunit: Fix formatting of KUNIT tests to meet the standard

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 14 Apr 2021 17:06:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Nico Pache <npache@...hat.com>, linux-kernel@...r.kernel.org
Cc:     Mark Brown <broonie@...nel.org>, brendanhiggins@...gle.com,
        netdev@...r.kernel.org, davidgow@...gle.com, rafael@...nel.org,
        mptcp@...ts.linux.dev, linux-m68k@...ts.linux-m68k.org,
        geert@...ux-m68k.org, tytso@....edu, skhan@...uxfoundation.org,
        davem@...emloft.net, gregkh@...uxfoundation.org,
        linux-ext4@...r.kernel.org, mathew.j.martineau@...ux.intel.com
Subject: Re: (subset) [PATCH v2 0/6] kunit: Fix formatting of KUNIT tests to meet the standard

On Wed, 14 Apr 2021 04:58:03 -0400, Nico Pache wrote:
> There are few instances of KUNIT tests that are not properly defined.
> This commit focuses on correcting these issues to match the standard
> defined in the Documentation.
> 
> Issues Fixed:
>  - tests should end in KUNIT_TEST, some fixes have been applied to
>    correct issues were KUNIT_TESTS is used or KUNIT is not mentioned.
>  - Tests should default to KUNIT_ALL_TESTS
>  - Tests configs tristate should have if !KUNIT_ALL_TESTS
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/6] kunit: ASoC: topology: adhear to KUNIT formatting standard
      commit: b5fb388da472a69858355560d803602e0ace1006

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark