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: Mon, 09 Sep 2024 18:56:45 +0000 [thread overview]
Message-ID: <bug-219192-217253-8tnBTzy5wr@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 #3 from Jonathan Cameron (jic23@kernel.org) ---
On Mon, 09 Sep 2024 14:31:02 +0000
bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219192
>
> Andy Shevchenko (andy.shevchenko@gmail.com) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |andy.shevchenko@gmail.com
>
> --- Comment #2 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
> Might be related (read discussion in full):
>
> https://lore.kernel.org/platform-driver-x86/Ztlto06GyFxLXz1y@smile.fi.intel.com/.
>
Thanks.
https://lore.kernel.org/platform-driver-x86/20240906031601.4yodvhurcyi26qb2@treble/
Looks like the relevant info. So current view from Josh seems to be that
it's a clang bug. Interesting to see if that holds up if reported to clang
folk (or if there is undefined behaviour none of us are seeing!)
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:[~2024-09-09 18:56 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 [this message]
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
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-8tnBTzy5wr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.