linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Petr Mladek <pmladek@suse.com>,
	 Steven Rostedt <rostedt@goodmis.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	 Sergey Senozhatsky <senozhatsky@chromium.org>,
	 Jonathan Corbet <corbet@lwn.net>,
	 John Ogness <john.ogness@linutronix.de>,
	 Andrew Morton <akpm@linux-foundation.org>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] hexdump: Allow skipping identical lines
Date: Tue, 24 Dec 2024 12:56:26 +0100	[thread overview]
Message-ID: <87frmdnvkl.fsf@bootlin.com> (raw)
In-Reply-To: <Zs3UrlufPJ9wVyep@smile.fi.intel.com> (Andy Shevchenko's message of "Tue, 27 Aug 2024 16:29:18 +0300")

Hi Andy,

On 27/08/2024 at 16:29:18 +03, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> On Tue, Aug 27, 2024 at 11:01:47AM +0200, Miquel Raynal wrote:
>> andriy.shevchenko@linux.intel.com wrote on Mon, 26 Aug 2024 20:32:20
>> +0300:
>> > On Mon, Aug 26, 2024 at 06:24:14PM +0200, Miquel Raynal wrote:
>
> ...
>
>> > Also here is the formal NAK till the series gains the test cases.
>> 
>> What test cases are you talking about?
>
> Anything meaningful you come up with to show that the printed data is
> what it's expected. The module has a complimentary test case,
> lib/test_hexdump.c. Without changes in that file, there is no go
> to what ever golden ideas you have.

I had a look. The tests never test the content of the kernel buffer,
while this is the only part that my changes have an impact on. These
tests verify the hex_dump_to_buffer() logic, but never how it is used
through the print_hex_dump_*() helpers.

In this series I am just enabling a new way to print the content of the
buffer, like for instance enabling a prefix, which is not directly
related to the core implementation of hexdump.

Hence, I am sorry, but I will disregard this request unless someone
comes up with a working idea which is worth the effort, considering the
minimum impact of this change and the fact that it is mostly (if not
only) for debugging purposes and will most likely never reach users.

Thanks,
Miquèl

  reply	other threads:[~2024-12-24 11:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 16:24 [PATCH 0/2] hexdump: Allow skipping identical lines Miquel Raynal
2024-08-26 16:24 ` [PATCH 1/2] hexdump: Convert the ascii boolean into a flag variable Miquel Raynal
2024-12-24 15:41   ` Andy Shevchenko
2024-08-26 16:24 ` [PATCH 2/2] hexdump: Allow skipping identical lines Miquel Raynal
2024-08-26 17:35   ` Andy Shevchenko
2024-08-27  9:13     ` Miquel Raynal
2024-08-27 13:36       ` Andy Shevchenko
2024-08-26 17:32 ` [PATCH 0/2] " Andy Shevchenko
2024-08-27  9:01   ` Miquel Raynal
2024-08-27 13:29     ` Andy Shevchenko
2024-12-24 11:56       ` Miquel Raynal [this message]
2024-12-24 15:49         ` Andy Shevchenko
2024-12-30 11:35           ` Miquel Raynal
2025-01-13 12:16             ` Andy Shevchenko

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=87frmdnvkl.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=john.ogness@linutronix.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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;
as well as URLs for NNTP newsgroup(s).