From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Vikram Pandita <vikram.pandita@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap: header: remove unused data-type
Date: Thu, 10 Dec 2009 12:10:31 +0200 [thread overview]
Message-ID: <20091210101031.GB14473@nokia.com> (raw)
In-Reply-To: <1260392121-16685-1-git-send-email-vikram.pandita@ti.com>
On Wed, Dec 09, 2009 at 09:55:21PM +0100, ext Vikram Pandita wrote:
>Remove unused data type omap_gpio_switch_config
>
>Thereby also get rid of following sparse warnings:
>arch/arm/plat-omap/include/plat/board.h :121:20:
> warning: dubious bitfield without explicit `signed' or `unsigned'
>arch/arm/plat-omap/include/plat/board.h :122:19:
> warning: dubious bitfield without explicit `signed' or `unsigned'
>arch/arm/plat-omap/include/plat/board.h :123:24:
> warning: dubious bitfield without explicit `signed' or `unsigned'
>
>Signed-off-by: Vikram Pandita <vikram.pandita@ti.com>
Acked-by: Felipe Balbi <felipe.balbi@nokia.com>
--
balbi
prev parent reply other threads:[~2009-12-10 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 20:55 [PATCH] omap: header: remove unused data-type Vikram Pandita
2009-12-10 10:10 ` Felipe Balbi [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=20091210101031.GB14473@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox