From: khilman@deeprootsystems•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V2] ARM: OMAP2+: PM: VP: minor pr_warn updates
Date: Thu, 25 Oct 2012 15:11:24 -0700 [thread overview]
Message-ID: <87pq46qk1f.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1351190236-23443-1-git-send-email-nm@ti.com> (Nishanth Menon's message of "Thu, 25 Oct 2012 13:37:16 -0500")
Nishanth Menon <nm@ti•com> writes:
> change pr_warnings to pr_warn and ensure a newline
> is present in all messages
>
> Cc: linux-omap at vger.kernel.org
> Cc: linux-arm-kernel at lists.infradead.org
>
> Signed-off-by: Nishanth Menon <nm@ti•com>
Thanks queuing for v3.8 as PM cleanup (branch: for_3.8/cleanup/pm.)
Kevin
prev parent reply other threads:[~2012-10-25 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 18:37 [PATCH V2] ARM: OMAP2+: PM: VP: minor pr_warn updates Nishanth Menon
2012-10-25 22:11 ` 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=87pq46qk1f.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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