From: Joe Perches <joe@perches.com>
To: Betty Dall <betty.dall@hp.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, infinipath@qlogic.com,
roland@kernel.org, sean.hefty@intel.com,
hal.rosenstock@gmail.com
Subject: Re: [PATCH] [Trivial] qib: fix an incorrect message
Date: Thu, 19 Jul 2012 12:11:50 -0700 [thread overview]
Message-ID: <1342725110.1988.36.camel@joe2Laptop> (raw)
In-Reply-To: <1342724170.28019.23.camel@ejdallLaptop>
On Thu, 2012-07-19 at 12:56 -0600, Betty Dall wrote:
> Thanks for the comment Joe. It looks like Roland already accepted the
> trivial change.
No worries.
> On Thu, 2012-07-19 at 11:03 -0700, Joe Perches wrote:
> > On Thu, 2012-07-19 at 13:34 -0600, Betty Dall wrote:
[]
> > > diff --git a/drivers/infiniband/hw/qib/qib_pcie.c b/drivers/infiniband/hw/qib/qib_pcie.c
> > []
> > > @@ -725,7 +725,7 @@ qib_pci_mmio_enabled(struct pci_dev *pdev)
> > > static pci_ers_result_t
> > > qib_pci_slot_reset(struct pci_dev *pdev)
> > > {
> > > - qib_devinfo(pdev, "QIB link_reset function called, ignored\n");
> > > + qib_devinfo(pdev, "QIB slot_reset function called, ignored\n");
> >
> > These sorts of typos can be avoided by using "%s: ", __func__
> >
> > qib_devinfo(pdev, "QIB %s: called, ignored\n", __func__);
>
> You are right about using __func__. That is what I use typically too. In
> this file, none of the qib_devinfo() messages use __func__, so I stuck
> with the trivial change for consistency. I could write another patch
> that makes use of __func__ for all the appropriate qib_devinfo() calls
> (there are 4 of them.) Do you think that is a worthwhile change? BTW, I
> did review all the other qib_devinfo() calls to make sure they are using
> the correct function names, and they look good.
Thanks for checking Betty.
It's hard for me to answer, I'm not the maintainer.
Maybe Roland has a preference.
I'd probably rename qib_devinfo to qib_info or qib_pdev_info
(adding an _ before info for consistency) and change the
macro definitions removing the unnecessary do {} while (0).
Single statement macros don't need to be:
#define macro(fmt, ...) \
do { \
single_stmt(fmt, ##__VA_ARGS__); \
} while (0)
and are probably better as:
#define macro(fmt, ...) \
single_stmt(fmt, ##__VA_ARGS__)
cheers, Joe
next prev parent reply other threads:[~2012-07-19 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 19:34 Betty Dall
2012-07-19 18:03 ` Joe Perches
2012-07-19 18:56 ` Betty Dall
2012-07-19 19:11 ` Joe Perches [this message]
2012-07-19 18:24 ` Roland Dreier
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=1342725110.1988.36.camel@joe2Laptop \
--to=joe@perches.com \
--cc=betty.dall@hp.com \
--cc=hal.rosenstock@gmail.com \
--cc=infinipath@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=trivial@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®