From: Andrew Morton <akpm@linux-foundation.org>
To: Jonathan Lassoff <jof@thejof.com>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] Add FAT messages to printk index
Date: Fri, 25 Mar 2022 13:18:14 -0700 [thread overview]
Message-ID: <20220325131814.7664f1d43c07b091548be2bf@linux-foundation.org> (raw)
In-Reply-To: <20220324021957.20173-1-jof@thejof.com>
On Thu, 24 Mar 2022 02:19:58 +0000 Jonathan Lassoff <jof@thejof.com> 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, while still enabling end users to detect changes and
> develop a semi-stable interface for detecting and parsing these messages.
>
> So that detailed FAT messages are captured by this printk index, this patch
> wraps fat_msg with a macro.
It would be nice to see some before-and-after sample output to help
reviewers understand this proposal.
> Reported-by: kernel test robot <lkp@intel.com>
We'll need a Signed-off-by: for this, please.
Documentation/process/submitting-patches.rst describes this.
next prev parent reply other threads:[~2022-03-25 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 2:19 Jonathan Lassoff
2022-03-24 5:45 ` OGAWA Hirofumi
2022-03-25 20:18 ` Andrew Morton [this message]
2022-03-31 0:51 ` Jonathan Lassoff
-- strict thread matches above, loose matches on Subject: below --
2022-03-18 17:23 Jonathan Lassoff
2022-03-18 19:56 ` OGAWA Hirofumi
2022-03-18 21:20 ` kernel test robot
2022-03-18 22:31 ` kernel test robot
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=20220325131814.7664f1d43c07b091548be2bf@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jof@thejof.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®