All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	David Brownell <dbrownell@users.sourceforge.net>,
	linux-next@vger.kernel.org,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: linux-next: NCR_700_detect warnings
Date: Tue, 10 Mar 2009 21:07:30 -0700	[thread overview]
Message-ID: <20090311040730.GA29678@kroah.com> (raw)
In-Reply-To: <d82e647a0903101859p1cc2adf6s375b389907a31b82@mail.gmail.com>

On Wed, Mar 11, 2009 at 09:59:09AM +0800, Ming Lei wrote:
> 2009/3/11 Geert Uytterhoeven <geert@linux-m68k.org>:
> > commit 76afea5b078d36ec080a75c29ff5a3fbc5774fee
> > Author: Ming Lei <tom.leiming@gmail.com>
> > Date:   Fri Feb 6 23:40:12 2009 +0800
> >
> >    platform driver: fix incorrect use of 'platform_bus_type' with 'struct devic
> >
> >    This patch fixes the bug reported in
> >        http://bugzilla.kernel.org/show_bug.cgi?id=11681.
> >
> >    "Lots of device drivers register a 'struct device_driver' with
> >    the '.bus' member set to '&platform_bus_type'. This is wrong,
> >    since the platform_bus functions expect the 'struct device_driver'
> >    to be wrapped up in a 'struct platform_driver' which provides
> >    some additional callbacks (like suspend_late, resume_early).
> >    The effect may be that platform_suspend_late() uses bogus data
> >    outside the device_driver struct as a pointer pointer to the
> >    device driver's suspend_late() function or other hard to
> >    reproduce failures."(Lothar Wassmann)
> >
> >    Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> >    Acked-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> >    Acked-by: David Brownell <dbrownell@users.sourceforge.net>
> >    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> >
> > This introduced the following warnings on m68k, as `dev' is now a
> > `struct platform_device *' instead of a `struct device *':
> >
> > | drivers/scsi/a4000t.c:64: warning: passing argument 3 of 'NCR_700_detect' from incompatible pointer type
> > | drivers/scsi/mvme16x_scsi.c:67: warning: passing argument 3 of 'NCR_700_detect' from incompatible pointer type
> > | drivers/scsi/bvme6000_scsi.c:61: warning: passing argument 3 of 'NCR_700_detect' from incompatible pointer type
> >
> > I think the below is missing (untested on real hardware)?
> 
> Yes, you are correct. It is really missed.

Great, Geert, care to resend with a signed-off-by: so I can apply this?

thanks,

greg k-h

      reply	other threads:[~2009-03-11  4:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 20:47 linux-next: NCR_700_detect warnings Geert Uytterhoeven
2009-03-11  1:59 ` Ming Lei
2009-03-11  1:59   ` Ming Lei
2009-03-11  4:07   ` Greg KH [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=20090311040730.GA29678@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@suse.de \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tom.leiming@gmail.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 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.