All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jiri Kosina <jikos@jikos.cz>
Subject: Re: linux-next: usb build failure
Date: Mon, 9 Jun 2008 19:13:47 -0700	[thread overview]
Message-ID: <20080610021347.GA11173@kroah.com> (raw)
In-Reply-To: <20080610115603.db3c1847.sfr@canb.auug.org.au>

On Tue, Jun 10, 2008 at 11:56:03AM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> Today's linux-next build (powerpc ppc64_defconfig) with the usb tree
> applied failed like this:
> 
> drivers/hid/usbhid/hiddev.c: In function 'hiddev_compat_ioctl':
> drivers/hid/usbhid/hiddev.c:767: warning: passing argument 1 of 'hiddev_ioctl' from incompatible pointer type
> drivers/hid/usbhid/hiddev.c:767: warning: passing argument 2 of 'hiddev_ioctl' makes integer from pointer without a cast
> drivers/hid/usbhid/hiddev.c:767: error: too many arguments to function 'hiddev_ioctl'
> 
> This was fixed in Jiri's hid tree on May 27 using a patch like that below
> (though this patch is more complete in that it removes the now unused
> inode variable).
> 
> You and Jiri should decide who is carrying the patch "USB: hiddev: Switch
> to unlocked_ioctl".  Currently it is in both the usb and the hid trees.

I'll drop it from mine, sorry, I was going to wait until I saw Jiri
apply it.

thanks,

greg k-h

  reply	other threads:[~2008-06-10  2:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  1:56 linux-next: usb build failure Stephen Rothwell
2008-06-10  2:13 ` Greg KH [this message]
2008-06-10  3:14   ` 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=20080610021347.GA11173@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jikos@jikos.cz \
    --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 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.