From: Martin Kelly <mkelly@xevo.com>
To: Jonathan Cameron <jic23@kernel.org>,
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 2/2] dt-bindings: iio:imu:mpu6050: support more interrupt types
Date: Mon, 23 Apr 2018 09:53:09 -0700 [thread overview]
Message-ID: <cf9a541f-d266-8ae5-9c59-b4a2661ffb54@xevo.com> (raw)
In-Reply-To: <20180421162801.4b8ddc25@archlinux>
On 04/21/2018 08:28 AM, Jonathan Cameron wrote:
> On Fri, 20 Apr 2018 19:05:12 +0200
> Jean-Baptiste Maneyrol <jmaneyrol@invensense.com> wrote:
>
>> On 20/04/2018 18:54, Martin Kelly wrote:
>>> Document that the hardware supports falling edge, rising edge, level
>>> low, and level high interrupt types, rather than just rising edge.
>>>
>>> The language used is the same as that in st_lsm6dsx.txt.
>>>
>>> Signed-off-by: Martin Kelly <mkelly@xevo.com>
> Hi Martin,
>
> Please pick up an acks / reviewed-by's from earlier versions.
> The chances are I'll miss them some of the time otherwise.
> Rob acked this one.
>
> Applied with the two acks I know of to the togreg branch of iio.git
> and pushed out as testing for the autobuilders to play with it.
>
> Thanks,
>
> Jonathan
>
OK, I'll try to remember to do that in the future.
next prev parent reply other threads:[~2018-04-23 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 16:54 [PATCH v7 1/2] iio:imu: inv_mpu6050: support more interrupt types Martin Kelly
2018-04-20 16:54 ` [PATCH v7 2/2] dt-bindings: iio:imu:mpu6050: " Martin Kelly
2018-04-20 17:05 ` Jean-Baptiste Maneyrol
2018-04-21 15:28 ` Jonathan Cameron
2018-04-23 16:53 ` Martin Kelly [this message]
2018-04-20 17:04 ` [PATCH v7 1/2] iio:imu: inv_mpu6050: " Jean-Baptiste Maneyrol
2018-04-21 15:25 ` Jonathan Cameron
2018-04-21 17:45 ` Martin Kelly
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=cf9a541f-d266-8ae5-9c59-b4a2661ffb54@xevo.com \
--to=mkelly@xevo.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=linux-iio@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).