From: Jonathan Cameron <jic23@kernel.org>
To: Adi <adinata.softwareengineer@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
lorenzo@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2 0/5] iio: humidity: hts221: update probe and logging implementations
Date: Sat, 22 Aug 2026 02:55:57 +0100 [thread overview]
Message-ID: <20260822025557.75714fd1@jic23-huawei> (raw)
In-Reply-To: <CABZ6vuAye2aO1BvhXjBAdAJFOmDGkQcXrPN3Bn-VhpEiQGXQog@mail.gmail.com>
On Mon, 17 Aug 2026 22:55:17 +0800
Adi <adinata.softwareengineer@gmail.com> wrote:
> > Looks like you've fixed up the stuff Andy pointed out in v1 and all looked
> > reasonable to me, so applied to the testing branch of iio.git.
> >
> > Note that branch will be rebased on 7.3-rc1 once available and only
> > then pushed out for linux-next to pick up.
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
>
> Thank you for the advice and help.
>
Added the tag.
Thanks
J
> Regards,
> Adi Nata
prev parent reply other threads:[~2026-08-22 1:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 15:31 [PATCH v2 0/5] iio: humidity: hts221: update probe and logging implementations Adi Nata
2026-08-13 15:31 ` [PATCH v2 1/5] iio: humidity: hts221: report available values via read_avail() Adi Nata
2026-08-13 15:31 ` [PATCH v2 2/5] iio: humidity: hts221: Add a blank line after variable declarations Adi Nata
2026-08-13 15:31 ` [PATCH v2 3/5] iio: humidity: hts221: Allow unknown whoami for DT fallback Adi Nata
2026-08-13 15:31 ` [PATCH v2 4/5] iio: humidity: hts221: use dev_err_probe() in probe paths Adi Nata
2026-08-13 15:31 ` [PATCH v2 5/5] iio: humidity: hts221: fix division by zero in calibration parsing Adi Nata
2026-08-17 0:49 ` [PATCH v2 0/5] iio: humidity: hts221: update probe and logging implementations Jonathan Cameron
2026-08-17 7:23 ` Andy Shevchenko
2026-08-17 14:55 ` Adi
2026-08-22 1:55 ` Jonathan Cameron [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=20260822025557.75714fd1@jic23-huawei \
--to=jic23@kernel.org \
--cc=adinata.softwareengineer@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--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