From: Kevin Hilman <khilman@ti.com>
To: "Mark A. Greer" <mgreer@animalcreek.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] arm: omap3: pm34xx.c: Some minor fixups
Date: Mon, 19 Mar 2012 14:43:54 -0700 [thread overview]
Message-ID: <87ehso5krp.fsf@ti.com> (raw)
In-Reply-To: <1332033768-21986-1-git-send-email-mgreer@animalcreek.com> (Mark A. Greer's message of "Sat, 17 Mar 2012 18:22:46 -0700")
"Mark A. Greer" <mgreer@animalcreek.com> writes:
> I found some minor issues when looking through pm34xx.c recently
> so these patches try to address them. My apologies if they are
> already fixed in another branch somewhere. Based on latest k.o.
> master branch.
Thanks Mark.
Queueing these for v3.4-rc.
Kevin
prev parent reply other threads:[~2012-03-19 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 1:22 [PATCH v3 0/2] arm: omap3: pm34xx.c: Some minor fixups Mark A. Greer
2012-03-18 1:22 ` [PATCH v3 1/2] arm: omap3: pm34xx.c: Fix omap3_pm_init() error out paths Mark A. Greer
2012-03-19 9:48 ` Tero Kristo
2012-03-20 9:17 ` Paul Walmsley
2012-03-20 14:02 ` Kevin Hilman
2012-03-18 1:22 ` [PATCH v3 2/2] arm: omap3: pm34xx.c: Replace printk() with appropriate pr_*() Mark A. Greer
2012-03-19 21:43 ` 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=87ehso5krp.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mgreer@animalcreek.com \
/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).