From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP2+: sparse fixes
Date: Sat, 11 Jul 2015 20:29:14 +0530 [thread overview]
Message-ID: <cover.1436622578.git.nsekhar@ti.com> (raw)
Hi Tony,
Here are some sparse fixes for mach-omap2.
After this series mach-omap2 is sparse clean.
Thanks,
Sekhar
Sekhar Nori (2):
ARM: OMAP2+: sparse: add missing static declaration
ARM: OMAP2+: sparse: add missing function declarations
arch/arm/mach-omap2/omap-mpuss-lowpower.c | 2 +-
arch/arm/mach-omap2/omap3-restart.c | 1 +
arch/arm/mach-omap2/omap4-restart.c | 1 +
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_81xx_data.c | 34 +++++++++++-----------
arch/arm/mach-omap2/pdata-quirks.c | 6 ++--
7 files changed, 25 insertions(+), 23 deletions(-)
--
2.4.4.408.g16da57c
next reply other threads:[~2015-07-11 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 14:59 Sekhar Nori [this message]
2015-07-11 14:59 ` [PATCH 1/2] ARM: OMAP2+: sparse: add missing static declaration Sekhar Nori
2015-07-16 5:41 ` Paul Walmsley
2015-07-11 14:59 ` [PATCH 2/2] ARM: OMAP2+: sparse: add missing function declarations Sekhar Nori
2015-07-16 5:43 ` 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=cover.1436622578.git.nsekhar@ti.com \
--to=nsekhar@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).