From: Rob Herring <robh@kernel.org>
To: "Randolph Maaßen" <gaireg@gaireg.de>
Cc: gaireg@gaireg.de, Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Mark Rutland <mark.rutland@arm.com>,
Brian Masney <masneyb@onstation.org>,
Jonathan Marek <jonathan@marek.ca>,
Douglas Fischer <fischerdouglasc@gmail.com>,
Martin Kelly <mkelly@xevo.com>,
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: imu: add icm20602 bindings to mpu6050
Date: Wed, 30 Jan 2019 13:49:42 -0600 [thread overview]
Message-ID: <20190130194942.GA30767@bogus> (raw)
In-Reply-To: <20190128185010.8275-1-gaireg@gaireg.de>
On Mon, 28 Jan 2019 19:50:02 +0100, =?UTF-8?q?Randolph=20Maa=C3=9Fen?= wrote:
> Adding the invensense ICM-20602 to the compatible list of the mpu6050
> driver
>
> Signed-off-by: Randolph Maaßen <gaireg@gaireg.de>
>
> ---
> Changes in v2:
> - write i2c disable register using reg_set instead of define
> - decide to write to i2c disable register based on reg_set instead of
> chip type
> ---
> Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-01-30 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 18:50 [PATCH v2 1/2] dt-bindings: iio: imu: add icm20602 bindings to mpu6050 Randolph Maaßen
2019-01-28 18:50 ` [PATCH v2 2/2] iio: imu: mpu6050: Add support for the ICM 20602 IMU Randolph Maaßen
2019-02-02 9:54 ` Jonathan Cameron
2019-01-30 19:49 ` Rob Herring [this message]
2019-02-02 9:52 ` [PATCH v2 1/2] dt-bindings: iio: imu: add icm20602 bindings to mpu6050 Jonathan Cameron
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=20190130194942.GA30767@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fischerdouglasc@gmail.com \
--cc=gaireg@gaireg.de \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=jonathan@marek.ca \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masneyb@onstation.org \
--cc=mkelly@xevo.com \
--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 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).