From: Joe Perches <joe@perches.com>
To: openipmi-developer@lists.sourceforge.net, linux-rdma@vger.kernel.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] treewide: Add and use dev_fmt similar to pr_fmt
Date: Wed, 9 May 2018 08:15:44 -0700 [thread overview]
Message-ID: <cover.1525878372.git.joe@perches.com> (raw)
The pr_fmt mechanism exists for pr_<level> logging message prefixing,
but no similar capability exists for dev_<level> message prefixing.
Many uses of dev_<level> have an embedded prefix for logging output.
So add a similar dev_fmt macro that can automatically prefix the
dev_<level> logging output.
Rename the existing dev_<level> functions to _dev_<level> and add new
macros that call _dev_<level> with the desired prefix if defined.
The new default #define for dev_fmt is blank.
Convert ipmi and infiniband to use this mechanism.
Miscellanea:
o x86/early-quirks uses an internal macro for #define dev_err which conflicts
with the existing dev_err macro, so rename it.
Joe Perches (6):
x86/early-quirks: Rename duplicate define of dev_err
device: Add #define dev_fmt similar to #define pr_fmt
ipmi: msghandler: Add and use pr_fmt and dev_fmt, remove PFX
ipmi: Use more common logging styles
ipmi: Convert printk(KERN_<level> to pr_<level>(
infiniband: qplib_fp: Use dev_fmt
arch/x86/kernel/early-quirks.c | 8 +-
drivers/base/core.c | 12 +--
drivers/char/ipmi/ipmi_bt_sm.c | 64 ++++++++--------
drivers/char/ipmi/ipmi_devintf.c | 11 ++-
drivers/char/ipmi/ipmi_kcs_sm.c | 4 +-
drivers/char/ipmi/ipmi_msghandler.c | 53 +++++++------
drivers/char/ipmi/ipmi_poweroff.c | 67 ++++++++---------
drivers/char/ipmi/ipmi_si_hardcode.c | 9 ++-
drivers/char/ipmi/ipmi_si_hotmod.c | 17 +++--
drivers/char/ipmi/ipmi_si_intf.c | 22 +++---
drivers/char/ipmi/ipmi_si_pci.c | 12 +--
drivers/char/ipmi/ipmi_si_platform.c | 20 ++---
drivers/char/ipmi/ipmi_smic_sm.c | 26 +++----
drivers/char/ipmi/ipmi_ssif.c | 73 +++++++++---------
drivers/char/ipmi/ipmi_watchdog.c | 52 +++++++------
drivers/infiniband/hw/bnxt_re/qplib_fp.c | 125 ++++++++++++++-----------------
include/linux/device.h | 103 ++++++++++++++-----------
17 files changed, 330 insertions(+), 348 deletions(-)
--
2.15.0
next reply other threads:[~2018-05-09 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:15 Joe Perches [this message]
2018-05-09 15:15 ` [PATCH 6/6] infiniband: qplib_fp: Use dev_fmt Joe Perches
2018-05-15 14:40 ` Doug Ledford
2018-05-15 15:01 ` Selvin Xavier
2018-05-09 16:47 ` [PATCH 0/6] treewide: Add and use dev_fmt similar to pr_fmt Corey Minyard
2018-05-09 17:04 ` Joe Perches
2018-05-09 17:22 ` Corey Minyard
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=cover.1525878372.git.joe@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).