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, linux-kernel@vger.kernel.org,
	Stefan Achatz <erazor_de@users.sourceforge.net>,
	Jiri Kosina <jikos@jikos.cz>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: linux-next: build warnings after merge of the driver-core tree
Date: Fri, 21 May 2010 09:47:30 -0700	[thread overview]
Message-ID: <20100521164730.GA11173@kroah.com> (raw)
In-Reply-To: <20100521161843.20e795db.sfr@canb.auug.org.au>

On Fri, May 21, 2010 at 04:18:43PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the driver-core tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
> 
> drivers/hid/hid-roccat-kone.c:694: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:696: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:701: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:703: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:708: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:710: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:715: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:717: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:722: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:724: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:729: warning: initialization from incompatible pointer type
> drivers/hid/hid-roccat-kone.c:731: warning: initialization from incompatible pointer type
> 
> Introduced by commit 867040163f10f2b52b45bc573f330d6eb28f5914 ("sysfs:
> add struct file* to bin_attr callbacks") from the driver-core tree
> interacting with commit 14bf62cde79423a02a590e02664ed29a36facec1 ("HID:
> add driver for Roccat Kone gaming mouse") from the hid tree.
> 
> I added the following patch:
> 
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri, 21 May 2010 16:15:32 +1000
> Subject: [PATCH] hid: fix hid-roccat-kone for bin_attr API change
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  drivers/hid/hid-roccat-kone.c |   24 ++++++++++++------------

That patch looks fine, but I can't take it in my tree as the HID tree
isn't merged with Linus's tree yet :(

thanks,

greg k-h

  parent reply	other threads:[~2010-05-21 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21  6:18 linux-next: build warnings after merge of the driver-core tree Stephen Rothwell
2010-05-21 16:22 ` Chris Wright
2010-05-21 16:47 ` Greg KH [this message]
2010-05-21 21:30   ` Jiri Kosina
2010-05-21 22:27     ` Greg KH
2010-05-24 14:03       ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2014-12-01  7:42 Stephen Rothwell
2014-12-01  7:45 ` Arend van Spriel
2014-12-01  7:45   ` Arend van Spriel
2014-12-02 18:09   ` 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=20100521164730.GA11173@kroah.com \
    --to=greg@kroah.com \
    --cc=chrisw@sous-sol.org \
    --cc=erazor_de@users.sourceforge.net \
    --cc=jikos@jikos.cz \
    --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 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.