From: Rupesh Majhi <zoone.rupert@gmail.com>
To: jic23@kernel.org
Cc: "Andy Shevchenko" <andy@kernel.org>,
"Bill Wendling" <morbo@google.com>,
"David Lechner" <dlechner@baylibre.com>,
"Eddie James" <eajames@linux.ibm.com>,
"Justin Stitt" <justinstitt@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v12 0/5] iio: pressure: dps310: hardware FIFO support
Date: Mon, 19 Oct 2026 00:24:43 +0300 [thread overview]
Message-ID: <20261018212443.43473-1-zoone.rupert@gmail.com> (raw)
In-Reply-To: <20261011145914.05d1c7a6@jic23-hlaptop>
On Sun, Oct 11, 2026 at 03:00:53PM +0100, Jonathan Cameron wrote:
> Applied patches 1-4. Not this was messy so there was some hand applying needed.
> Please check I didn't mess it up!
Checked, matches what I sent.
> I replied with my view on patch 5 in the earlier thread (just now), but definitely
> open to hearing more opinions on how far we want to go with annotations.
Fine to drop it.
prev parent reply other threads:[~2026-10-18 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 19:50 Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 1/5] iio: pressure: dps310: use devm_mutex_init() Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 2/5] iio: pressure: dps310: read buffered samples from the hardware FIFO Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 3/5] iio: pressure: dps310: derive the drain interval from the watermark Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 4/5] iio: pressure: dps310: implement .hwfifo_flush_to_buffer() Rupesh Majhi
2026-10-03 19:50 ` [PATCH v12 5/5] iio: pressure: dps310: assert the lock at runtime too Rupesh Majhi
2026-10-11 14:00 ` [PATCH v12 0/5] iio: pressure: dps310: hardware FIFO support Jonathan Cameron
2026-10-18 21:24 ` Rupesh Majhi [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=20261018212443.43473-1-zoone.rupert@gmail.com \
--to=zoone.rupert@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=eajames@linux.ibm.com \
--cc=jic23@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®