From: Tony Lindgren <tony@atomide.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 00/11] OMAP2/TWL: Fix Sparse warnings
Date: Thu, 16 Sep 2010 12:34:25 -0700 [thread overview]
Message-ID: <20100916193425.GM29610@atomide.com> (raw)
In-Reply-To: <1282856209-15645-1-git-send-email-manjugk@ti.com>
* G, Manjunath Kondaiah <manjugk@ti.com> [100826 13:50]:
> This patch series fixes sparse warnings for OMAP and TWL code.
> For better readabilty the patches are categorised based on type of
> sparse warnigns.
>
> The sparse warning logs are embedded with each patch followed
> by fix.
>
> Build and boot tested on omap3 with omap3_defconfig.
>
> Manjunatha GK (11):
> OMAP: mach-omap2: Fix incorrect assignment warnings
> OMAP: mach-omap2: Fix static declaration warnings
> OMAP: mach-omap2: Fix static function warnings
> OMAP: mach-omap2: Fix miscellaneous sparse warnings
> OMAP: plat-omap: Fix static function warnings
> OMAP: McBSP: Fix static function warning
> OMAP: HSMMC: Fix unused variable warning
> OMAP: NAND: Fix static declaration warning
> TWL CORE: Fix sparse warning
> TWL IRQ: Fix fucntion declaration warnings
> TWL4030: Codec: Fix fucntion declaration error
Looks like these are almost ready to go. Please repost against
v2.6.36-rc4 with linux-arm-kernel list Cc'd. Also check that
the related driver list is Cc'd.
Then, assuming no more comments, can you set up a git
branch somewhere for me to pull? For more info, see
"Merging patches using git" at:
http://www.elinux.org/OMAP_patch_merging_process#Patch_submission_checklist
Regards,
Tony
next prev parent reply other threads:[~2010-09-16 19:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 20:56 [PATCH 00/11] OMAP2/TWL: Fix Sparse warnings G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 01/11] OMAP: mach-omap2: Fix incorrect assignment warnings G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 02/11] OMAP: mach-omap2: Fix static declaration warnings G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 03/11] OMAP: mach-omap2: Fix static function warnings G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 04/11] OMAP: mach-omap2: Fix miscellaneous sparse warnings G, Manjunath Kondaiah
2010-09-16 19:27 ` Tony Lindgren
2010-09-20 5:57 ` G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 05/11] OMAP: plat-omap: Fix static function warnings G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 06/11] OMAP: McBSP: Fix static function warning G, Manjunath Kondaiah
2010-08-31 7:34 ` Peter Ujfalusi
2010-08-26 20:56 ` [PATCH 07/11] OMAP: HSMMC: Fix unused variable warning G, Manjunath Kondaiah
2010-08-27 9:03 ` kishore kadiyala
2010-08-26 20:56 ` [PATCH 08/11] OMAP: NAND: Fix static declaration warning G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 09/11] TWL CORE: Fix sparse warning G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 10/11] TWL IRQ: Fix fucntion declaration warnings G, Manjunath Kondaiah
2010-08-26 20:56 ` [PATCH 11/11] TWL4030: Codec: Fix fucntion declaration error G, Manjunath Kondaiah
2010-08-31 7:32 ` Peter Ujfalusi
2010-09-16 19:34 ` Tony Lindgren [this message]
2010-09-20 5:58 ` [PATCH 00/11] OMAP2/TWL: Fix Sparse warnings G, Manjunath Kondaiah
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=20100916193425.GM29610@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=nm@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.