From: Jonathan Cameron <jic23@kernel.org>
To: Martin Kepplinger <martink@posteo.de>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: mma8452: add i2c_device_id for mma8451
Date: Tue, 15 Mar 2016 22:05:45 +0000 [thread overview]
Message-ID: <56E88739.6070204@kernel.org> (raw)
In-Reply-To: <1457955194-6222-1-git-send-email-martink@posteo.de>
On 14/03/16 11:33, Martin Kepplinger wrote:
> This was forgotten about and is added for consistency now
>
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
> ---
> I'm sorry, I messed up the first patch. Understandable though, given
> it's complexity.
Took me a disturbingly long time to notice what was wrong.
Applied to the togreg branch of iio.git - pushed out as testing
for the autobuilders to play with it.
Jonathan
>
>
> drivers/iio/accel/mma8452.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/accel/mma8452.c b/drivers/iio/accel/mma8452.c
> index 305ed0e..6aa2517 100644
> --- a/drivers/iio/accel/mma8452.c
> +++ b/drivers/iio/accel/mma8452.c
> @@ -1535,6 +1535,7 @@ static const struct dev_pm_ops mma8452_pm_ops = {
> };
>
> static const struct i2c_device_id mma8452_id[] = {
> + { "mma8451", mma8451 },
> { "mma8452", mma8452 },
> { "mma8453", mma8453 },
> { "mma8652", mma8652 },
>
prev parent reply other threads:[~2016-03-15 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 11:26 [PATCH 1/2] iio: mma8452: add i2c_device_id for mma8451 Martin Kepplinger
2016-03-14 11:26 ` [PATCH 2/2] iio: mma8452: use runtime pm instead of device specific autosleep Martin Kepplinger
2016-03-15 22:07 ` Jonathan Cameron
2016-03-14 11:33 ` [PATCH 1/2] iio: mma8452: add i2c_device_id for mma8451 Martin Kepplinger
2016-03-15 22:05 ` Jonathan Cameron [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=56E88739.6070204@kernel.org \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=pmeerw@pmeerw.net \
/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.