The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Md Shofiqul Islam <shofiqtest@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, lars@metafoo.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: health: max30102: Add timestamp to FIFO data
Date: Sat, 16 May 2026 14:39:16 -0700 (PDT)	[thread overview]
Message-ID: <6a08e404.9cb0d8e3.2c93a2.545b@mx.google.com> (raw)
In-Reply-To: <20260515160434.7749e240@jic23-huawei>

On Fri, 15 May 2026 16:04:34 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> Generally don't add features to a driver you aren't using - they
> end up as dead code.

Understood. Dropping this patch. The scan_index = -1 design and the
per-sample timestamp problem both make this a non-starter without a
much more substantial rework.

Thank you for the review.

Md Shofiqul Islam

      reply	other threads:[~2026-05-16 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 20:03 [PATCH] iio: health: max30102: Add timestamp to FIFO data Md Shofiqul Islam
2026-05-15 15:04 ` Jonathan Cameron
2026-05-16 21:39   ` Md Shofiqul Islam [this message]

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=6a08e404.9cb0d8e3.2c93a2.545b@mx.google.com \
    --to=shofiqtest@gmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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