mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Jonathan Lassoff <jof@thejof.com>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Andrew Morton <akpm@linux-foundation.org>,
	Chris Down <chris@chrisdown.name>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] Add FAT messages to printk index
Date: Mon, 4 Apr 2022 15:50:04 +0200	[thread overview]
Message-ID: <20220404135003.GA22550@pathway.suse.cz> (raw)
In-Reply-To: <8aaa2dd7995e820292bb40d2120ab69756662c65.1648688136.git.jof@thejof.com>

On Wed 2022-03-30 17:58:00, Jonathan Lassoff wrote:
> In order for end users to quickly react to new issues that come up in
> production, it is proving useful to leverage the printk indexing system.
> This printk index enables kernel developers to use calls to printk()
> with changable ad-hoc format strings (as they always have; no change
> of expectations), while enabling end users to examine format strings to
> detect changes.
> Since end users are using regular expressions to match messages printed
> through printk(), being able to detect changes in chosen format strings
> from release to release provides a useful signal to review
> printk()-matching regular expressions for any necessary updates.
> 
> So that detailed FAT messages are captured by this printk index, this patch
> wraps fat_msg with a macro.
> 
> Signed-off-by: Jonathan Lassoff <jof@thejof.com>
> Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

Reviewed-by: Petr Mladek <pmladek@suse.com>
Tested-by: Petr Mladek <pmladek@suse.com>

Best Regards,
Petr

      reply	other threads:[~2022-04-04 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31  0:51 Jonathan Lassoff
2022-03-31  0:58 ` Jonathan Lassoff
2022-04-04 13:50   ` Petr Mladek [this message]

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=20220404135003.GA22550@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris@chrisdown.name \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jof@thejof.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®