From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 219192] drivers/iio/imu/adis16400.o: warning: objtool: adis16400_write_raw() falls through to next function adis16400_show_flash_count()
Date: Sat, 25 Jan 2025 11:39:46 +0000 [thread overview]
Message-ID: <bug-219192-217253-6vE0I5wcHD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219192-217253@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219192
--- Comment #12 from Jonathan Cameron (jic23@kernel.org) ---
On Thu, 23 Jan 2025 17:45:29 +0000
bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219192
>
> --- Comment #11 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
> Do we still have this issue in the latest vanilla (v6.13)? Looking again at
> the
> code I'm wondering why we can't simply use guard()() instead of
> scoped_guard().
> It might actually fix this.
>
Is this actually a bug rather than a false warning?
My impression was that this is a compiler problem and I'm not that keen to
modify
drivers to work around that unless the resulting module is actually broken.
If we have to, just add pointless returns instead of unreachable() markings
with a comment to say they are unreachable but we suppressing a toolchain
issue.
Jonathan
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-01-25 11:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 9:35 [Bug 219192] New: drivers/iio/imu/adis16400.o: warning: objtool: adis16400_write_raw() falls through to next function adis16400_show_flash_count() bugzilla-daemon
2024-08-25 9:35 ` [Bug 219192] " bugzilla-daemon
2024-08-26 10:11 ` [Bug 219192] New: " Jonathan Cameron
2024-08-26 10:11 ` [Bug 219192] " bugzilla-daemon
2024-09-09 14:31 ` bugzilla-daemon
2024-09-09 18:56 ` Jonathan Cameron
2024-09-09 18:56 ` bugzilla-daemon
2024-09-10 5:42 ` bugzilla-daemon
2024-09-14 11:37 ` Jonathan Cameron
2024-09-14 11:37 ` bugzilla-daemon
2024-10-02 21:24 ` bugzilla-daemon
2024-10-06 10:49 ` Jonathan Cameron
2024-10-06 10:49 ` bugzilla-daemon
2024-10-06 19:51 ` bugzilla-daemon
2024-10-18 11:02 ` bugzilla-daemon
2024-10-18 17:39 ` Jonathan Cameron
2024-10-18 17:39 ` bugzilla-daemon
2025-01-23 17:45 ` bugzilla-daemon
2025-01-25 11:39 ` Jonathan Cameron
2025-01-25 11:39 ` bugzilla-daemon [this message]
2025-04-30 6:33 ` bugzilla-daemon
2025-05-05 12:02 ` Jonathan Cameron
2025-05-05 12:02 ` bugzilla-daemon
2026-03-17 16:42 ` bugzilla-daemon
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=bug-219192-217253-6vE0I5wcHD@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-iio@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