linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Michael Hennerich <michael.hennerich@analog.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH 3/3] Input: adxl34x - Fix references to adx134x
Date: Fri, 11 Feb 2011 08:55:02 -0800	[thread overview]
Message-ID: <20110211165502.GA17932@core.coreip.homeip.net> (raw)
In-Reply-To: <4D55563E.4050309@analog.com>

On Fri, Feb 11, 2011 at 04:31:10PM +0100, Michael Hennerich wrote:
> On 02/11/2011 04:33 PM, Mark Brown wrote:
> > The adxl34x SPI driver has what appears to be a typo referring to the
> > device as adx134x with the numeral 1 rather than letter l. This appears
> > to be an error so convert.
> >
> > Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> >   
> Thought I fixed that before...
> Acked-by: Michael Hennerich <michael.hennerich@analog.com>
> 

One must have slipped through... Anyway, applied the whole lot.

Thanks.

-- 
Dmitry

      reply	other threads:[~2011-02-11 16:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 15:33 [PATCH 1/3] Input: adxl34x-i2c - Convert to dev_pm_ops Mark Brown
2011-02-11 15:31 ` Michael Hennerich
2011-02-11 15:33 ` [PATCH 2/3] Input: adxl34x-spi " Mark Brown
2011-02-11 15:31   ` Michael Hennerich
2011-02-11 15:33 ` [PATCH 3/3] Input: adxl34x - Fix references to adx134x Mark Brown
2011-02-11 15:31   ` Michael Hennerich
2011-02-11 16:55     ` 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=20110211165502.GA17932@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-input@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    /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).