public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Tobias Klauser <tklauser@distanz•ch>,
	John Linn <john.linn@xilinx•com>
Subject: Re: linux-next: input tree build failure
Date: Sun, 24 Jan 2010 22:46:03 -0800	[thread overview]
Message-ID: <20100125064602.GA22833@core.coreip.homeip.net> (raw)
In-Reply-To: <20100125165219.cd0b869d.sfr@canb.auug.org.au>

On Mon, Jan 25, 2010 at 04:52:19PM +1100, Stephen Rothwell wrote:
> Hi Dmitry,
> 
> Today's linux-next build (powerpc ppc44x_defconfig) failed like this:
> 
> drivers/input/serio/xilinx_ps2.c: In function 'xps2_of_probe':
> drivers/input/serio/xilinx_ps2.c:273: error: incompatible type for argument 1 of 'resource_size'
> include/linux/ioport.h:132: note: expected 'const struct resource *' but argument is of type 'struct resource'
> drivers/input/serio/xilinx_ps2.c: In function 'xps2_of_remove':
> drivers/input/serio/xilinx_ps2.c:347: error: incompatible type for argument 1 of 'resource_size'
> include/linux/ioport.h:132: note: expected 'const struct resource *' but argument is of type 'struct resource'
> 
> Please at least build test this stuff ...
> 
> Caused by commit cc7bbfa322b48be82b1c86a104433d4ac349da79 ("Input:
> xilinx_ps2 - use resource_size").
> 
> I have reverted that commit for today.
> 

Argh, sorry about that. I adjusted the commit; John, Tobias, please
verify (next branch in my tree).

Thanks.

-- 
Dmitry

  reply	other threads:[~2010-01-25  6:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25  5:52 linux-next: input tree build failure Stephen Rothwell
2010-01-25  6:46 ` Dmitry Torokhov [this message]
2010-01-25  7:26   ` Tobias Klauser
  -- strict thread matches above, loose matches on Subject: below --
2009-12-07  9:03 Stephen Rothwell
2009-12-07 16:25 ` Randy Dunlap
2009-12-07 17:36   ` Dmitry Torokhov
2009-12-07 22:16     ` Stephen Rothwell
2009-03-10  4:49 Stephen Rothwell
2009-03-10  5:02 ` Dmitry Torokhov
2009-03-10  5:14   ` Stephen Rothwell
2008-08-19  6:31 Stephen Rothwell
2008-08-19 13:01 ` Dmitry Torokhov
2008-08-19 19:59   ` Greg KH
2008-08-19 20:00 ` Greg KH
2008-08-20  5:49   ` Stephen Rothwell
2008-08-20 18:35     ` Greg KH
2008-08-22 20:29     ` Dmitry Torokhov
2008-08-22 22:15       ` Alfred E. Heggestad
2008-08-25  0:01         ` 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=20100125064602.GA22833@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail$(echo .)com \
    --cc=john.linn@xilinx$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tklauser@distanz$(echo .)ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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