Linux IIO development
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
	Mehdi Djait <mehdi.djait.k@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, linux-iio@vger.kernel.org
Subject: Re: Questions: iio: accel: kionix-kx022a: timestamp when using the data-rdy trigger?
Date: Fri, 17 Feb 2023 19:02:07 +0200	[thread overview]
Message-ID: <cde24815-bfe4-9347-f950-ed8497edd4ca@gmail.com> (raw)
In-Reply-To: <20230217152713.000007ee@Huawei.com>

On 2/17/23 17:27, Jonathan Cameron wrote:
> On Fri, 17 Feb 2023 15:43:26 +0100
> Mehdi Djait <mehdi.djait.k@gmail.com> wrote:
> 
>> On Fri, Feb 17, 2023 at 02:28:28PM +0000, Jonathan Cameron wrote:
>>> On Fri, 17 Feb 2023 13:59:16 +0200
>>> Matti Vaittinen <mazziesaccount@gmail.com> wrote:
>>>    
>>>> On 2/17/23 13:43, Jonathan Cameron wrote:
>>>>> On Fri, 17 Feb 2023 07:56:22 +0200
>>>>> Matti Vaittinen <mazziesaccount@gmail.com> wrote:
>>>>>      
>>>>>> Hi Mehdi,
>>>>>>
>>>>>> On 2/16/23 22:22, Mehdi Djait wrote: 

>>
>> So should I send a patch with data->timestamp as I suggested ?
> 
> I think so.

Please do! That would be very much appreciated :)

Yours,
	-- Matti

-- 
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~


  reply	other threads:[~2023-02-17 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 20:22 Questions: iio: accel: kionix-kx022a: timestamp when using the data-rdy trigger? Mehdi Djait
2023-02-17  5:56 ` Matti Vaittinen
2023-02-17 11:43   ` Jonathan Cameron
2023-02-17 11:59     ` Matti Vaittinen
2023-02-17 14:28       ` Jonathan Cameron
2023-02-17 14:43         ` Mehdi Djait
2023-02-17 15:27           ` Jonathan Cameron
2023-02-17 17:02             ` Matti Vaittinen [this message]
2023-02-17 18:47               ` Mehdi Djait

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=cde24815-bfe4-9347-f950-ed8497edd4ca@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mehdi.djait.k@gmail.com \
    /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