From: Kevin Hilman <khilman@baylibre.com>
To: Nishanth Menon <nm@ti.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Joe Perches <joe@perches.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] smartreflex: Neaten logging
Date: Thu, 18 Aug 2016 13:26:57 -0500 [thread overview]
Message-ID: <m2r39mq6fi.fsf@baylibre.com> (raw)
In-Reply-To: <ef0d3152-a01a-9359-bfb5-3fb8ab1b6041@ti.com> (Nishanth Menon's message of "Fri, 12 Aug 2016 07:46:30 -0500")
Nishanth Menon <nm@ti.com> writes:
> On 08/12/2016 02:14 AM, Joe Perches wrote:
>> Use a more common logging style.
>>
>> Miscellanea:
>>
>> o Use pr_warn
>> o Coalesce formats adding missing spaces
>> o Argument alignment
>> o Remove unnecessary OOM messages as k.alloc does stack dumps
>>
>> Signed-off-by: Joe Perches <joe@perches.com>
>
> Acked-by: Nishanth Menon <nm@ti.com>
>
> Kevin, would you be able to pick this up?
Acked-by: Kevin Hilman <khilman@baylibre.com>
Rafael, please apply directly. I don't have any other smartreflex
changes for this cycle.
Kevin
prev parent reply other threads:[~2016-08-19 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 7:14 [PATCH] smartreflex: Neaten logging Joe Perches
2016-08-12 12:46 ` Nishanth Menon
2016-08-18 18:26 ` Kevin Hilman [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=m2r39mq6fi.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.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