From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Dmitry Torokhov <dtor@mail.ru>
Subject: Re: [PATCH] mfd/stmpe: allow for const keyboard data
Date: Wed, 9 May 2012 16:55:23 +0200 [thread overview]
Message-ID: <20120509145523.GK1794@sortiz-mobl> (raw)
In-Reply-To: <1335184124-9105-1-git-send-email-linus.walleij@stericsson.com>
Hi Linus,
On Mon, Apr 23, 2012 at 02:28:44PM +0200, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> Since it's not like we will re-arrange the keys at run-time, it
> seems proper to allow the keymap data to be const. This solves
> a compilation warning in ux500.
>
> Cc: Dmitry Torokhov <dtor@mail.ru>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> include/linux/mfd/stmpe.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Patch applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-05-09 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:28 Linus Walleij
2012-05-09 14:55 ` Samuel Ortiz [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=20120509145523.GK1794@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=dtor@mail.ru \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®