From: "Hanne-Lotta Mäenpää" <hannelotta@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-iio@vger.kernel.org, bigeasy@linutronix.de,
spasswolf@web.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: hid-sensors: Use software trigger
Date: Tue, 14 Apr 2026 12:30:59 +0300 [thread overview]
Message-ID: <461bc8a7-b2e8-469d-8988-2f080e23a624@gmail.com> (raw)
In-Reply-To: <20260412143840.349400ca@jic23-huawei>
On 4/12/26 4:38 PM, Jonathan Cameron wrote:
> The patch was merged a while ago and in the discussions in the related
> threads we decide it was too invasive to handle as a fix for what is a
> warning print, not a failure.
>
> The closes tag without a fixes would trigger various bot warnings.
> It could have been there as a Link however.
>
> Also, the small temporal issue of the fix predating the bugzilla
> entry made it trickier! I could have added it when merging but
> we didn't have confirmation that the two were definitely the same
> issue at that time and I chose not to connect up the dots.
>
> Your reply may well help anyone looking to find the issue though
> so thanks for that.
>
> Jonathan
>
>
Thanks for replying. The warning doesn't appear in kernel v7.0.0-rc-7.
Good to know about the Closes / Fixes tags.
Best Regards,
Hanne-Lotta Mäenpää
prev parent reply other threads:[~2026-04-14 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 22:45 [PATCH v2] iio: hid-sensors: Use software trigger Srinivas Pandruvada
2026-03-01 12:42 ` Jonathan Cameron
2026-03-23 15:10 ` Hanne-Lotta Mäenpää
2026-04-12 13:38 ` Jonathan Cameron
2026-04-14 9:30 ` Hanne-Lotta Mäenpää [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=461bc8a7-b2e8-469d-8988-2f080e23a624@gmail.com \
--to=hannelotta@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spasswolf@web.de \
--cc=srinivas.pandruvada@linux.intel.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