From: Greg KH <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/4] kernel/panic: return early from print_tainted() when not tainted
Date: Tue, 4 Jun 2024 17:33:51 +0200 [thread overview]
Message-ID: <2024060443-improve-undermost-0cf7@gregkh> (raw)
In-Reply-To: <01d6c03de1c9d1b52b59c652a3704a0a9886ed63.1717146197.git.jani.nikula@intel.com>
On Fri, May 31, 2024 at 12:04:54PM +0300, Jani Nikula wrote:
> Reduce indent to make follow-up changes slightly easier on the eyes.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> kernel/panic.c | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2024-06-04 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 9:04 [PATCH 0/4] kernel/panic: add more descriptive logging of kernel taints Jani Nikula
2024-05-31 9:04 ` [PATCH 1/4] kernel/panic: return early from print_tainted() when not tainted Jani Nikula
2024-06-04 15:33 ` Greg KH [this message]
2024-05-31 9:04 ` [PATCH 2/4] kernel/panic: convert print_tainted() to use struct seq_buf internally Jani Nikula
2024-06-04 15:34 ` Greg KH
2024-05-31 9:04 ` [PATCH 3/4] kernel/panic: initialize taint_flags[] using a macro Jani Nikula
2024-06-04 15:34 ` Greg KH
2024-05-31 9:04 ` [PATCH 4/4] kernel/panic: add verbose logging of kernel taints in backtraces Jani Nikula
2024-06-04 15:34 ` Greg KH
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=2024060443-improve-undermost-0cf7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jani.nikula@intel.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