public inbox for linux-kernel@vger.kernel.org
 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, 27 Aug 2024 11:01:47 +0200	[thread overview]
Message-ID: <20240827110147.29a7481a@xps-13> (raw)
In-Reply-To: <Zsy8JPaiGknBypw9@smile.fi.intel.com>

Hi Andy,

Thanks for your feedback.

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:
> > Hello!
> > 
> > While working on NAND issues, I used print_hex_dump() a lot to compare
> > data. But I am mostly working on embedded systems where the kernel
> > messages go through a serial console. Sometimes network support is an
> > option, sometimes not. Anyway, I often print buffers both in kernel
> > space and user space to compare them, and they may be full of 0's or
> > 1's, which means lines are repeated a lot in the output and this is slow
> > *and* hard to compare.
> > 
> > I initially hacked into lib/hexdump.c for my own purpose and just
> > discarded all the other users, but it felt like this might be a useful
> > feature for others and decided to make it a public patch.
> > 
> > * First patch changes the "ascii" parameter into a "flags" variable now
> >   accepting the value: DUMP_FLAG_ASCII.
> > * Second patch adds a new flag to skip the identical lines, because this
> >   must be an opt-in parameter, I guess.  
> 
> This is quite a long to look into, can you please add a summary here which
> includes (but not limited to) the following:
> 1) examples before and after (ah, I see you have that in the patch 2,
>    but would be still good to have in the cover letter);

No problem, I can make this part of the cover letter as well.

> 2) excerpts of the code for before and after (since the type of the ascii
>    parameter had been changed).

In patch 1/2 there is the Coccinelle script, but I must admit the
syntax is not super clear, so I will improve this by showing the two
main user cases with a proper human-readable diff.

> Also here is the formal NAK till the series gains the test cases.

What test cases are you talking about?

Thanks,
Miquèl

  reply	other threads:[~2024-08-27  9:01 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 [this message]
2024-08-27 13:29     ` Andy Shevchenko
2024-12-24 11:56       ` Miquel Raynal
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=20240827110147.29a7481a@xps-13 \
    --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