linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Samuel Ortiz <sameo@linux.intel.com>, Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH -v2 02/10] mfd: intel: Constify struct mfd_cell where possible
Date: Mon, 18 Nov 2013 14:32:58 +0100	[thread overview]
Message-ID: <1384781586-4798-2-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1384781586-4798-1-git-send-email-geert@linux-m68k.org>

As of commit 03e361b25ee8dfb1fd9b890072c23c4aae01c6c7 ("mfd: Stop setting
refcounting pointers in original mfd_cell arrays"), the "cell" parameter of
mfd_add_devices() is "const" again. Hence make all cell data passed to
mfd_add_devices() const where possible.

Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
v2: Split in groups

 drivers/mfd/intel_msic.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/mfd/intel_msic.c b/drivers/mfd/intel_msic.c
index 9203d47cdbb1..049fd23af54a 100644
--- a/drivers/mfd/intel_msic.c
+++ b/drivers/mfd/intel_msic.c
@@ -178,7 +178,7 @@ static struct mfd_cell msic_devs[] = {
  * These devices appear only after the MSIC driver itself is initialized so
  * we can guarantee that the SCU IPC interface is ready.
  */
-static struct mfd_cell msic_other_devs[] = {
+static const struct mfd_cell msic_other_devs[] = {
 	/* Audio codec in the MSIC */
 	{
 		.id			= -1,
-- 
1.7.9.5


  reply	other threads:[~2013-11-18 13:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 13:32 [PATCH -v2 01/10] mfd: dialog: Constify struct mfd_cell where possible Geert Uytterhoeven
2013-11-18 13:32 ` Geert Uytterhoeven [this message]
2013-11-18 13:32 ` [PATCH -v2 03/10] mfd: marvell: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 04/10] mfd: maxim: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 05/10] mfd: stmicro: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 06/10] mfd: ti: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 07/10] mfd: toshiba: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 08/10] mfd: wolfson: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 09/10] mfd: staging: " Geert Uytterhoeven
2013-11-21 11:02   ` Lee Jones
2013-11-21 15:16     ` Greg Kroah-Hartman
2013-11-18 13:33 ` [PATCH -v2 10/10] mfd: " Geert Uytterhoeven
2013-11-18 14:29 ` [PATCH -v2 01/10] mfd: dialog: " Lee Jones

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=1384781586-4798-2-git-send-email-geert@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).