From: Samuel Ortiz <sameo@linux.intel.com>
To: Joe Perches <joe@perches.com>
Cc: Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [resend PATCH] nfc: logging neatening
Date: Tue, 7 Apr 2015 12:07:38 +0200 [thread overview]
Message-ID: <20150407100738.GA9511@ribalta.mp.intel.com> (raw)
In-Reply-To: <1428391020.20888.31.camel@perches.com>
Hi Joe,
On Tue, Apr 07, 2015 at 12:17:00AM -0700, Joe Perches wrote:
> Add missing terminating newlines to nfc_info and nfc_err
> to avoid possible interleaving from other messages.
>
> Miscellanea:
>
> o typo fix of "unknonwn" in message
> o remove unnecessary OOM messages as there's a generic dump_stack()
> o realign arguments
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>
> Adding Andrew Morton
> Resending after a 8 weeks with no reply/review.
>
> drivers/nfc/microread/i2c.c | 2 +-
> drivers/nfc/nfcmrvl/main.c | 4 ++--
> drivers/nfc/nfcmrvl/usb.c | 18 +++++++++---------
> drivers/nfc/pn533.c | 2 +-
> drivers/nfc/pn544/i2c.c | 7 ++-----
> drivers/nfc/port100.c | 36 ++++++++++++++++++------------------
> drivers/nfc/st21nfcb/i2c.c | 5 +----
> drivers/nfc/st21nfcb/ndlc.c | 5 ++---
> 8 files changed, 36 insertions(+), 43 deletions(-)
Sorry for the lag. Patch applied to nfc-next now.
Cheers,
Samuel.
next prev parent reply other threads:[~2015-04-07 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 7:17 [resend PATCH] nfc: logging neatening Joe Perches
2015-04-07 10:07 ` Samuel Ortiz [this message]
2015-04-07 13:42 ` Joe Perches
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=20150407100738.GA9511@ribalta.mp.intel.com \
--to=sameo@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aloisio.almeida@openbossa.org \
--cc=joe@perches.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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