[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250312192811.7632a936@pumpkin>
Date: Wed, 12 Mar 2025 19:28:11 +0000
From: David Laight <david.laight.linux@...il.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>, Linus Torvalds
<torvalds@...ux-foundation.org>, Christophe Leroy
<christophe.leroy@....fr>, Rasmus Villemoes <linux@...musvillemoes.dk>,
nnac123@...ux.ibm.com, horms@...nel.org
Subject: Re: [PATCH next 2/8] test_hexdump: Create test output data from the
binary input data buffer
On Mon, 10 Mar 2025 10:31:10 +0200
Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> On Sat, Mar 08, 2025 at 09:34:46AM +0000, David Laight wrote:
> > Using the same data that is passed to hex_dump_to_buffer() lets
> > the tests be expanded to test different input data bytes.
>
> Do we really need to kill the static test cases?
> Are they anyhow harmful?
>
I was asked to add some extra tests for other byte values.
The static result buffers just get in the way.
They are also not necessary since the tests are comparing the output
of two (hopefully) different implementations and checking they are
the same.
David
Powered by blists - more mailing lists