From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: benve@cisco.com, ssujith@cisco.com, _govind@gmx.com,
neepatel@cisco.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cisco: enic: Update logging macros and uses
Date: Fri, 11 Mar 2016 15:08:12 -0500 (EST) [thread overview]
Message-ID: <20160311.150812.1296153063421521729.davem@davemloft.net> (raw)
In-Reply-To: <fd7e962bc72778fc1f2a9b21742eff2eb19d9bd8.1457474066.git.joe@perches.com>
From: Joe Perches <joe@perches.com>
Date: Tue, 8 Mar 2016 13:54:56 -0800
> Don't hide varibles used by the logging macros.
>
> Miscellanea:
>
> o Use the more common ##__VA_ARGS__ extension
> o Add missing newlines to formats
> o Realign arguments
>
> Signed-off-by: Joe Perches <joe@perches.com>
Applied, thanks Joe.
prev parent reply other threads:[~2016-03-11 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 21:54 [PATCH] cisco: enic: Update logging macros and uses Joe Perches
2016-03-11 20:08 ` David Miller [this message]
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=20160311.150812.1296153063421521729.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=_govind@gmx.com \
--cc=benve@cisco.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neepatel@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=ssujith@cisco.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;
as well as URLs for NNTP newsgroup(s).