From: Joe Perches <joe@perches.com>
To: linux-usb@vger.kernel.org
Cc: Jan Dumon <j.dumon@option.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] hso: neatening
Date: Fri, 2 Sep 2016 15:58:00 -0700 [thread overview]
Message-ID: <cover.1472856901.git.joe@perches.com> (raw)
This seems to be the only code in the kernel that uses
macro defines with a trailing underscore. Fix that.
Joe Perches (2):
hso: Use a more common logging style
hso: Convert printk to pr_<level>
drivers/net/usb/hso.c | 118 +++++++++++++++++++++++---------------------------
1 file changed, 55 insertions(+), 63 deletions(-)
--
2.10.0.rc2.1.g053435c
next reply other threads:[~2016-09-02 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 22:58 Joe Perches [this message]
2016-09-02 22:58 ` [PATCH 1/2] hso: Use a more common logging style Joe Perches
2016-09-02 22:58 ` [PATCH 2/2] hso: Convert printk to pr_<level> Joe Perches
2016-09-06 20:30 ` [PATCH 0/2] hso: neatening David Miller
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.1472856901.git.joe@perches.com \
--to=joe@perches.com \
--cc=j.dumon@option.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).