From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP: resolve sparse warnings with v3.8-rc1
Date: Sun, 23 Dec 2012 18:24:56 -0700 [thread overview]
Message-ID: <20121224012304.13698.43551.stgit@dusk.lan> (raw)
Another minor release, another new set of sparse warnings. It would
be good if patch submitters and mainline committers can verify that
new patches don't add sparse warnings. Otherwise it makes it harder
for others to verify that their code is sparse-warning-free.
- Paul
---
sparse_fixes_a_3.8-rc
text data bss dec hex filename
7697036 722268 5614832 14034136 d624d8 vmlinux.omap2plus_defconfig.orig
7697036 722268 5614832 14034136 d624d8 vmlinux.omap2plus_defconfig
Paul Walmsley (3):
ARM: OMAP: 32k counter: resolve sparse warnings
ARM: OMAP AM33xx: hwmod data: resolve sparse warnings
ARM: OMAP: SRAM: resolve sparse warnings
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 4 ++-
arch/arm/plat-omap/counter_32k.c | 2 ++
arch/arm/plat-omap/counter_32k.h | 20 ++++++++++++++++
arch/arm/plat-omap/sram.c | 2 ++
arch/arm/plat-omap/sram.h | 35 ++++++++++++++++++++++++++++
5 files changed, 61 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/plat-omap/counter_32k.h
create mode 100644 arch/arm/plat-omap/sram.h
next reply other threads:[~2012-12-24 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 1:24 Paul Walmsley [this message]
2012-12-24 1:24 ` [PATCH 1/3] ARM: OMAP: 32k counter: resolve sparse warnings Paul Walmsley
2012-12-25 16:22 ` Santosh Shilimkar
2013-01-01 18:13 ` Tony Lindgren
2013-01-02 19:36 ` Paul Walmsley
2012-12-24 1:25 ` [PATCH 2/3] ARM: OMAP AM33xx: hwmod data: " Paul Walmsley
2012-12-26 4:10 ` Mugunthan V N
2012-12-24 1:25 ` [PATCH 3/3] ARM: OMAP: SRAM: " Paul Walmsley
2013-01-01 18:15 ` Tony Lindgren
2013-01-02 19:37 ` Paul Walmsley
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=20121224012304.13698.43551.stgit@dusk.lan \
--to=paul@pwsan.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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).