All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Alan Cox <alan@linux.intel.com>,
	linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] input: cy8ctmg100_ts: signedness bug
Date: Fri, 06 Aug 2010 07:40:49 +0000	[thread overview]
Message-ID: <20100806074049.GQ9031@bicker> (raw)
In-Reply-To: <20100806064609.GA27764@core.coreip.homeip.net>

On Thu, Aug 05, 2010 at 11:46:09PM -0700, Dmitry Torokhov wrote:
> 
> Thanks Dan. It looks like cy8ctmg110_write_regs has siilar issue. Do you
> thiks the following will work?
> 
> Thanks.
> 

Ah right.  That should be signed as well.  Thanks.

regards,
dan carpenter



WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Alan Cox <alan@linux.intel.com>,
	linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] input: cy8ctmg100_ts: signedness bug
Date: Fri, 6 Aug 2010 09:40:49 +0200	[thread overview]
Message-ID: <20100806074049.GQ9031@bicker> (raw)
In-Reply-To: <20100806064609.GA27764@core.coreip.homeip.net>

On Thu, Aug 05, 2010 at 11:46:09PM -0700, Dmitry Torokhov wrote:
> 
> Thanks Dan. It looks like cy8ctmg110_write_regs has siilar issue. Do you
> thiks the following will work?
> 
> Thanks.
> 

Ah right.  That should be signed as well.  Thanks.

regards,
dan carpenter



  reply	other threads:[~2010-08-06  7:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06  6:30 [patch] input: cy8ctmg100_ts: signedness bug Dan Carpenter
2010-08-06  6:30 ` Dan Carpenter
2010-08-06  6:46 ` Dmitry Torokhov
2010-08-06  6:46   ` Dmitry Torokhov
2010-08-06  7:40   ` Dan Carpenter [this message]
2010-08-06  7:40     ` Dan Carpenter
2010-08-06 11:20 ` Alan Cox
2010-08-06 11:20   ` Alan Cox

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=20100806074049.GQ9031@bicker \
    --to=error27@gmail.com \
    --cc=alan@linux.intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    /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.