From: Rob Herring <robh@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,mpu6880
Date: Wed, 9 Dec 2020 13:59:32 -0600 [thread overview]
Message-ID: <20201209195932.GA845313@robh.at.kernel.org> (raw)
In-Reply-To: <20201202104656.5119-1-stephan@gerhold.net>
On Wed, 02 Dec 2020 11:46:55 +0100, Stephan Gerhold wrote:
> MPU-6880 seems to be very similar to MPU-6500 / MPU-6050 and it works
> fine with some minor additions for the mpu6050 driver.
> Add a compatible for it to the binding documentation.
>
> Cc: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> Note: This applies only on top of the patch for the YAML conversion:
> https://lore.kernel.org/linux-iio/20201128173343.390165-3-jic23@kernel.org/
> I guess that one will be applied very soon so I think this is easier :)
>
> Changes in v2: None :)
> ---
> .../devicetree/bindings/iio/imu/invensense,mpu6050.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-12-09 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 10:46 [PATCH v2 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,mpu6880 Stephan Gerhold
2020-12-02 10:46 ` [PATCH v2 2/2] iio: imu: inv_mpu6050: Add support for MPU-6880 Stephan Gerhold
2020-12-02 13:21 ` Jean-Baptiste Maneyrol
2020-12-02 13:20 ` [PATCH v2 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,mpu6880 Jean-Baptiste Maneyrol
2020-12-09 19:59 ` Rob Herring [this message]
2020-12-13 13:27 ` 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=20201209195932.GA845313@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.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.