From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] OMAP: TWL: sparse fixes
Date: Tue, 04 Jan 2011 14:44:46 -0800 [thread overview]
Message-ID: <1294181086.18162.38.camel@localhost> (raw)
In-Reply-To: <8762u47dmk.fsf@ti.com>
On Tue, 2011-01-04 at 10:00 -0800, Kevin Hilman wrote:
> Nishanth Menon <nm@ti.com> writes:
>
> > Source:
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
> > branch: omap-for-linus
> >
> > Doing a rm arch/arm/mach-omap2/*.o;make C=1 arch/arm/mach-omap2/
> > resulted in the following sparse warnings:
> > http://pastebin.mozilla.org/907954
> >
> > This series fixes the twl warnings
> > Nishanth Menon (2):
> > OMAP2+: TWL: make conversion routines static
> > OMAP2+: TWL: include pm header for init protos
> >
> > arch/arm/mach-omap2/omap_twl.c | 10 ++++++----
> > 1 files changed, 6 insertions(+), 4 deletions(-)
>
> Acked-by: Kevin Hilman <khilman@ti.com>
>
> Tony, these should probably queue for .38 if it's not too late.
On second thought, it's too late for the main 2.6.38 merge window for
these. I'll queue these in my pm-fixes branch for the 2.6.38-rc cycle.
Kevin
prev parent reply other threads:[~2011-01-04 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 18:58 [PATCH 0/2] OMAP: TWL: sparse fixes Nishanth Menon
2011-01-03 18:58 ` [PATCH 1/2] OMAP2+: TWL: make conversion routines static Nishanth Menon
2011-01-03 18:58 ` [PATCH 2/2] OMAP2+: TWL: include pm header for init protos Nishanth Menon
2011-01-03 22:36 ` [PATCH 0/2] OMAP: TWL: sparse fixes Russell King - ARM Linux
2011-01-03 22:39 ` Nishanth Menon
2011-01-04 20:37 ` Nishanth Menon
2011-01-05 0:25 ` Russell King - ARM Linux
2011-01-05 13:32 ` Nishanth Menon
2011-01-04 18:00 ` Kevin Hilman
2011-01-04 22:44 ` 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=1294181086.18162.38.camel@localhost \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).