From: Josh Poimboeuf <jpoimboe@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Peter Zijlstra <peterz@infradead.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH 0/3] some objtool warnings fixes
Date: Mon, 9 Mar 2026 09:03:04 -0700 [thread overview]
Message-ID: <cover.1773071991.git.jpoimboe@kernel.org> (raw)
Some fixes for objtool warnings reported by Arnd.
Josh Poimboeuf (3):
objtool: Fix Clang jump table detection
ASoC: codecs: wcd9335: Remove potential undefined behavior in
wcd9335_slimbus_irq()
iio: imu: bmi160: Remove potential undefined behavior in
bmi160_config_pin()
drivers/iio/imu/bmi160/bmi160_core.c | 2 ++
sound/soc/codecs/wcd9335.c | 2 +-
tools/objtool/check.c | 5 ++---
3 files changed, 5 insertions(+), 4 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-09 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 16:03 Josh Poimboeuf [this message]
2026-03-09 16:03 ` [PATCH 1/3] objtool: Fix Clang jump table detection Josh Poimboeuf
2026-03-18 8:25 ` [tip: objtool/urgent] " tip-bot2 for Josh Poimboeuf
2026-03-09 16:03 ` [PATCH 2/3] ASoC: codecs: wcd9335: Remove potential undefined behavior in wcd9335_slimbus_irq() Josh Poimboeuf
2026-03-09 16:05 ` Mark Brown
2026-03-09 16:13 ` Josh Poimboeuf
2026-03-09 17:45 ` Srinivas Kandagatla
2026-03-09 16:03 ` [PATCH 3/3] iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() Josh Poimboeuf
2026-03-09 16:16 ` Nuno Sá
2026-03-09 16:27 ` Josh Poimboeuf
2026-03-09 16:31 ` Nuno Sá
2026-03-09 16:48 ` Josh Poimboeuf
2026-03-09 16:40 ` Andy Shevchenko
2026-03-09 16:52 ` David Lechner
2026-03-09 16:55 ` Josh Poimboeuf
2026-03-09 22:36 ` (subset) [PATCH 0/3] some objtool warnings fixes Mark Brown
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=cover.1773071991.git.jpoimboe@kernel.org \
--to=jpoimboe@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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.