From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: steve.glendinning@shawell.net, gregkh@linuxfoundation.org,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] smsc: Add logging message newlines
Date: Sun, 25 Nov 2012 16:15:19 -0500 (EST) [thread overview]
Message-ID: <20121125.161519.2093456773586153692.davem@davemloft.net> (raw)
In-Reply-To: <1353756469.6558.3.camel@joe-AO722>
From: Joe Perches <joe@perches.com>
Date: Sat, 24 Nov 2012 03:27:49 -0800
> Avoid any possible message logging interleaving by adding
> missing newlines.
>
> Align arguments.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Applied.
prev parent reply other threads:[~2012-11-25 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 11:27 [PATCH] smsc: Add logging message newlines Joe Perches
2012-11-25 21:15 ` 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=20121125.161519.2093456773586153692.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
/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).