linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-input <linux-input@vger.kernel.org>,
	Joe Rouvier <joe@rouvier.org>
Subject: Re: [PATCH] input: strict_strtoul takes unsigned long
Date: Tue, 23 Dec 2008 04:12:24 -0500	[thread overview]
Message-ID: <20081223091224.GB14302@anvil.corenet.prv> (raw)
In-Reply-To: <1228176260.5482.12.camel@brick>

On Mon, Dec 01, 2008 at 04:04:20PM -0800, Harvey Harrison wrote:
> Fix sparse warning introduced by:
> commit 160f1fef7e52e974489b3c70fbd4e094c06965c2 Input: convert drivers to use strict_strtoul()
> 

Applied, thank you Harvey.

-- 
Dmitry

      reply	other threads:[~2008-12-23  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  0:04 [PATCH] input: strict_strtoul takes unsigned long Harvey Harrison
2008-12-23  9:12 ` Dmitry Torokhov [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=20081223091224.GB14302@anvil.corenet.prv \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=joe@rouvier.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).