From: David Lechner <dlechner@baylibre.com>
To: Daniel Schaefer <dhs@frame.work>, Jonathan Cameron <jic23@kernel.org>
Cc: "srinivas pandruvada" <srinivas.pandruvada@linux.intel.com>,
"Jiri Kosina" <jikos@kernel.org>, "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Sven Vainküla" <sven@xn--vainkla-r2a.ee>,
linux@frame.work
Subject: Re: [PATCH] iio: hid-sensor: als: scale each channel individually
Date: Wed, 5 Aug 2026 07:53:04 -0500 [thread overview]
Message-ID: <2f9d39b3-efc2-4d50-98f2-71bc19e78ab6@baylibre.com> (raw)
In-Reply-To: <CAAjcXz5Y7W69LaUsFg323rTsd7waaSnLkD=dJYJvOCwPV2Apmg@mail.gmail.com>
On 8/4/26 8:23 PM, Daniel Schaefer wrote:
>> I'll queue it up on the testing branch of iio.git but more eyes welcome if
> anyone has time to take a look.
>
> Sorry I'm not sure what that means. Is the patch applied or
> should I send another one with commit message update?
It means that it is accepted/applied.
The iio/testing branch is the first step where various CI bots
will do some automatic checks. If they find something, you will
be notified. Otherwise nothing more for you to do (unless a serious
concern is raised later).
And it means there is still time for further review too in case
anyone wants to add their e.g. reviewed-by tag.
prev parent reply other threads:[~2026-08-05 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 17:18 [PATCH] iio: hid-sensor: als: scale each channel individually Daniel Schaefer via B4 Relay
2026-07-25 23:18 ` Jonathan Cameron
2026-07-27 15:18 ` srinivas pandruvada
2026-07-27 21:13 ` Jonathan Cameron
2026-07-28 0:38 ` Daniel Schaefer
2026-08-05 1:23 ` Daniel Schaefer
2026-08-05 12:53 ` David Lechner [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=2f9d39b3-efc2-4d50-98f2-71bc19e78ab6@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=dhs@frame.work \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@frame.work \
--cc=nuno.sa@analog.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sven@xn--vainkla-r2a.ee \
/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