From: Gregor Boirie <gregor.boirie@parrot.com>
To: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Cc: <lars@metafoo.de>
Subject: Re: [RFC PATCH v1 3/3] iio: make drivers use new timestamping clock API
Date: Mon, 15 Feb 2016 10:11:03 +0100 [thread overview]
Message-ID: <56C19627.4030800@parrot.com> (raw)
In-Reply-To: <56BF3B61.1020004@kernel.org>
On 02/13/2016 03:19 PM, Jonathan Cameron wrote:
> On 11/02/16 10:04, Gregor Boirie wrote:
>> Update IIO drivers to pass IIO device as argument to iio_get_time_ns() and
>> iio_get_time_res().
>>
>> Signed-off-by: Gregor Boirie <gregor.boirie@parrot.com>
> Clearly you need to be careful to ensure we can build the drivers
> when only patch one is applied. I'd be tempted to just merge this
> into patch one. Even more fun with patch 2 vs this.
> You could work some nasty macro magic, or go through a double name
> change, but given the nature of the patches, perhaps leave them as
> is for review and I'll splice them into a single patch at time of
> application - uggly but simple ;)
Ok. I'll merge all 3 patches for final submission.
>
> Otherwise looks fine to me.
>
> Jonathan
>
gregor
next prev parent reply other threads:[~2016-02-15 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 10:04 [RFC PATCH v1 0/3] iio: introduce timestamping clock selection Gregor Boirie
2016-02-11 10:04 ` [RFC PATCH v1 1/3] iio:core: timestamping clock selection support Gregor Boirie
2016-02-13 14:14 ` Jonathan Cameron
2016-02-14 17:43 ` Lars-Peter Clausen
2016-02-15 9:42 ` Gregor Boirie
2016-02-17 19:38 ` Jonathan Cameron
2016-02-18 9:25 ` Gregor Boirie
2016-02-11 10:04 ` [RFC PATCH v1 2/3] iio:core: timestamping clock resolution support Gregor Boirie
2016-02-11 10:04 ` [RFC PATCH v1 3/3] iio: make drivers use new timestamping clock API Gregor Boirie
2016-02-13 14:19 ` Jonathan Cameron
2016-02-15 9:11 ` Gregor Boirie [this message]
2016-02-13 14:12 ` [RFC PATCH v1 0/3] iio: introduce timestamping clock selection 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=56C19627.4030800@parrot.com \
--to=gregor.boirie@parrot.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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).