From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: david-b@pacbell.net, linux-kernel@vger.kernel.org,
g.liakhovetski@pengutronix.de
Subject: Re: [patch 2.6.26-rc5] gpio: sysfs interface (updated)
Date: Tue, 22 Jul 2008 16:50:56 -0700 [thread overview]
Message-ID: <20080722165056.799223a7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080722232824.GA22596@kroah.com>
On Tue, 22 Jul 2008 16:28:24 -0700
Greg KH <greg@kroah.com> wrote:
> On Tue, Jul 22, 2008 at 04:27:51PM -0700, Andrew Morton wrote:
> > On Thu, 12 Jun 2008 11:53:36 -0700
> > David Brownell <david-b@pacbell.net> wrote:
> >
> > > This adds a simple sysfs interface for GPIOs.
> >
> > device_create_drvdata() has magically vanished from today's linux-next,
> > so this code doesn't compile any more.
> >
> > This:
> >
> > --- a/drivers/gpio/gpiolib.c~gpio-sysfs-interface-updated-gpio-linux-next-fixes-for-sysfs-support-fix
> > +++ a/drivers/gpio/gpiolib.c
> > @@ -453,8 +453,8 @@ int gpio_export(unsigned gpio, bool dire
> > if (status == 0) {
> > struct device *dev;
> >
> > - dev = device_create_drvdata(&gpio_class, desc->chip->dev, 0,
> > - desc, "gpio%d", gpio);
> > + dev = device_create(&gpio_class, desc->chip->dev, 0, desc,
> > + "gpio%d", gpio);
>
> Should be NULL instead of 0 there, otherwise sparse will complain.
The third arg to device_create is a dev_t, so 0 is correct
Confused.
next prev parent reply other threads:[~2008-07-22 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 18:53 [patch 2.6.26-rc5] gpio: sysfs interface (updated) David Brownell
2008-07-22 23:27 ` Andrew Morton
2008-07-22 23:28 ` Greg KH
2008-07-22 23:39 ` Andrew Morton
2008-07-22 23:51 ` Greg KH
2008-07-22 23:50 ` Andrew Morton [this message]
2008-07-23 0:02 ` Greg KH
2008-07-23 0:01 ` David Brownell
2008-07-23 0:11 ` Greg KH
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=20080722165056.799223a7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=g.liakhovetski@pengutronix.de \
--cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.