From: Joe Perches <joe@perches.com>
To: Jason Baron <jbaron@akamai.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86/e820: Use pr_debug to avoid spamming dmesg log with debug messages
Date: Fri, 14 May 2021 10:38:58 -0700 [thread overview]
Message-ID: <7cc30a8a6644bb60e5f3358e89253d9fc783fe54.camel@perches.com> (raw)
In-Reply-To: <5a416031-ddcd-7ef4-ec33-47134bf064bb@akamai.com>
On Tue, 2021-05-11 at 17:31 -0400, Jason Baron wrote:
> That said, I do see the value in not having to open code the branch stuff, and
> making pr_debug() consistent with printk which does return a value. So that
> makes sense to me.
IMO: printk should not return a value.
next prev parent reply other threads:[~2021-05-14 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 19:38 [PATCH 0/2] " Heiner Kallweit
2021-05-03 19:39 ` [PATCH 1/2] dyndbg: add pr_debug return value if dynamic debugging is enabled Heiner Kallweit
2021-05-03 19:40 ` [PATCH 2/2] x86/e820: Use pr_debug to avoid spamming dmesg log with debug messages Heiner Kallweit
2021-05-05 16:58 ` Jason Baron
2021-05-05 18:40 ` Heiner Kallweit
2021-05-11 3:21 ` Jason Baron
2021-05-11 20:36 ` Heiner Kallweit
2021-05-11 21:31 ` Jason Baron
2021-05-14 17:38 ` Joe Perches [this message]
2021-05-14 19:56 ` Jason Baron
2021-05-14 20:22 ` Joe Perches
2021-05-14 20:32 ` Jason Baron
2021-05-14 21:15 ` Heiner Kallweit
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=7cc30a8a6644bb60e5f3358e89253d9fc783fe54.camel@perches.com \
--to=joe@perches.com \
--cc=bp@alien8.de \
--cc=hkallweit1@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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®