public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dmitry Torokhov <dmitry.torokhov@gmail•com>
Cc: Tero Saarni <tero.saarni@gmail•com>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: input tree build warnings
Date: Sat, 20 Jun 2009 17:17:43 +1000	[thread overview]
Message-ID: <20090620171743.1ef11ef2.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090620060559.GA7710@dtor-d630.eng.vmware.com>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

Hi Dmitry, Tero,

On Fri, 19 Jun 2009 23:06:09 -0700 Dmitry Torokhov <dmitry.torokhov@gmail•com> wrote:
>
> On Sat, Jun 13, 2009 at 12:54:50AM +0300, Tero Saarni wrote:
> > On Fri, 2009-06-12 at 17:05 +1000, Stephen Rothwell wrote:
> > > Hi Dmitry,
> > > 
> > > Today's linux-next build (x86_64 allmodconfig) produced these warnings:
> > > 
> > > drivers/input/evdev.c: In function 'evdev_do_ioctl':
> > > drivers/input/evdev.c:632: warning: comparison of distinct pointer types lacks a cast
> > > drivers/input/evdev.c:660: warning: comparison of distinct pointer types lacks a cast
> > > 
> > > Introduced by commit 61c7bfcdf5acee06f58b246d6615989134719d19 ("Input:
> > > synaptics - add support for reporting x/y resolution").
> > 
> > My mistake, thanks for the heads up!
> 
> I folded it into the original patch.

Thanks.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-06-20  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  7:05 linux-next: input tree build warnings Stephen Rothwell
2009-06-12 21:54 ` Tero Saarni
2009-06-20  6:06   ` Dmitry Torokhov
2009-06-20  7:17     ` Stephen Rothwell [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=20090620171743.1ef11ef2.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dmitry.torokhov@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tero.saarni@gmail$(echo .)com \
    /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