public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: driver-core tree build warning
Date: Mon, 13 Jul 2009 14:23:59 -0700	[thread overview]
Message-ID: <200907131423.59963.david-b@pacbell.net> (raw)
In-Reply-To: <20090713171802.GB22728@kroah.com>

On Monday 13 July 2009, Greg KH wrote:
> David, care to send patches fixing these warnings?

Here's a single patch:

=================== CUT HERE
From: David Brownell <dbrownell@users.sourceforge.net>

Some more attribute group pointers need to become const-friendly:

drivers/firewire/core-device.c:315: warning: assignment from incompatible pointer type
drivers/mtd/mtdcore.c:227: warning: initialization from incompatible pointer type
drivers/block/cciss.c:582: warning: initialization from incompatible pointer type

Two of these post-date the original constification patch; not sure
how I missed Firewire the first time.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
---
 drivers/block/cciss.c          |    2 +-
 drivers/firewire/core-device.c |    2 +-
 drivers/mtd/mtdcore.c          |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

--- a/drivers/block/cciss.c
+++ b/drivers/block/cciss.c
@@ -572,7 +572,7 @@ static struct attribute_group cciss_dev_
 	.attrs = cciss_dev_attrs,
 };
 
-static struct attribute_group *cciss_dev_attr_groups[] = {
+static const struct attribute_group *cciss_dev_attr_groups[] = {
 	&cciss_dev_attr_group,
 	NULL
 };
--- a/drivers/firewire/core-device.c
+++ b/drivers/firewire/core-device.c
@@ -312,7 +312,7 @@ static void init_fw_attribute_group(stru
 	group->groups[0] = &group->group;
 	group->groups[1] = NULL;
 	group->group.attrs = group->attrs;
-	dev->groups = group->groups;
+	dev->groups = (const struct attribute_group **) group->groups;
 }
 
 static ssize_t modalias_show(struct device *dev,
--- a/drivers/mtd/mtdcore.c
+++ b/drivers/mtd/mtdcore.c
@@ -217,7 +217,7 @@ struct attribute_group mtd_group = {
 	.attrs		= mtd_attrs,
 };
 
-struct attribute_group *mtd_groups[] = {
+struct const attribute_group *mtd_groups[] = {
 	&mtd_group,
 	NULL,
 };


  reply	other threads:[~2009-07-13 21:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  7:26 linux-next: driver-core tree build warning Stephen Rothwell
2009-07-13  7:28 ` Stephen Rothwell
2009-07-13  7:51   ` Stephen Rothwell
2009-07-13 17:18     ` Greg KH
2009-07-13 21:23       ` David Brownell [this message]
2009-07-13 21:27         ` Greg KH
2009-07-13 21:36         ` Greg KH
2009-07-14  0:44           ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2010-01-19  6:27 Stephen Rothwell
2010-01-19 21:04 ` Greg KH
2010-01-19 23:45   ` Stephen Rothwell
2010-01-20  6:25     ` Stephen Rothwell
2010-01-20  6:44       ` Stephen Rothwell
2010-01-21 23:10         ` Greg KH
2010-01-21 23:20           ` Stephen Rothwell
2010-01-29  7:21           ` Stephen Rothwell
2010-02-03  2:22             ` Greg KH
2010-02-03  3:29               ` Stephen Rothwell
2010-02-04  7:10               ` Stephen Rothwell

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=200907131423.59963.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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