public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
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, 26 Aug 2024 10:11:43 +0000	[thread overview]
Message-ID: <bug-219192-217253-CQKwJPN9Bh@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 #1 from Jonathan Cameron (jic23@kernel.org) ---
On Sun, 25 Aug 2024 09:35:37 +0000
bugzilla-daemon@kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219192
> 
>             Bug ID: 219192
>            Summary: drivers/iio/imu/adis16400.o: warning: objtool:
>                     adis16400_write_raw() falls through to next function
>                     adis16400_show_flash_count()
>            Product: Drivers
>            Version: 2.5
>           Hardware: All
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: IIO
>           Assignee: drivers_iio@kernel-bugs.kernel.org
>           Reporter: ionut_n2001@yahoo.com
>         Regression: No
> 
> drivers/iio/imu/adis16400.o: warning: objtool: adis16400_write_raw() falls
> through to next function adis16400_show_flash_count()
> 
> Kernel: 6.11.0-rc5 vanilla
> GCC compiler: gcc (Debian 14.1.0-5) 14.1.0

I think this is a false positive.  None of the cases of the switch statement
fail to return and there are unreachable() markings that this
check seems to not be able to see which were added to try and
point out to the compiler that it was failing to identify they
were not possible to get to.

We could add some returns the unreachable paths to work around
this warning I suppose.

Maybe we are doing something wrong otherwise?  I'd like more
eyes on this incase I'm just missing something obvious.

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.

  parent reply	other threads:[~2024-08-26 10:11 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 ` bugzilla-daemon [this message]
2024-09-09 14:31 ` [Bug 219192] " 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
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-CQKwJPN9Bh@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