From: Johannes Berg <johannes@sipsolutions.net>
To: Stefan Hansson <newbyte@postmarketos.org>,
Stefan Hansson <newbie13xd@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH] wifi: rsi: Fix types to appease CFI
Date: Sun, 02 Aug 2026 20:52:46 +0200 [thread overview]
Message-ID: <35231759dc9633edf72a745d0079897c000ff5ea.camel@sipsolutions.net> (raw)
In-Reply-To: <ba0fbf6a-024d-425c-aed3-ab0ee67246d4@postmarketos.org>
On Sun, 2026-08-02 at 20:40 +0200, Stefan Hansson wrote:
> Hello Johannes,
>
> On 02/08/2026 18:24, Johannes Berg wrote:
> > On Sun, 2026-08-02 at 14:22 +0200, Stefan Hansson wrote:
> > > Avoids errors like:
> > >
> > > CFI failure at kthread+0x124/0x1cc (target: rsi_coex_scheduler_thread+0x0/0x1b4 [redpine_91x]; expected type: 0x89fb613d)
> >
> > Yeah, well. Everyone gets _one_ warning to send patches that actually
> > build warning-free, after that I just drop them without notice...
>
> Could you clarify what you are referring to here? I don't get any errors
> when building after applying this patch on top of next-20260730:
Alright, so it does build, sorry. I was just looking at nipa:
https://patchwork.kernel.org/project/linux-wireless/patch/20260802-rsi-cfi-fix-v1-1-5821d2cb54ee@postmarketos.org/
But I see now it's just duplicating the kernel-doc issues across all the
builds ... I wasn't paying attention to _what_ it was reporting and the
kthread_complete_and_exit() use in the functions and thought it was
likely getting "control reaches end of non-void function" warnings since
you change functions to int without ever returning anything.
> If you are referring to checkpatch.pl complaining about the
> aforementioned error line being too long, I can wrap it if you prefer that.
Nah, that's fine, no worries.
johannes
prev parent reply other threads:[~2026-08-02 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260802-rsi-cfi-fix-v1-1-5821d2cb54ee@postmarketos.org>
2026-08-02 14:30 ` [PATCH] wifi: rsi: Fix types to appease CFI Jeff Johnson
2026-08-02 18:44 ` Stefan Hansson
2026-08-02 16:24 ` Johannes Berg
2026-08-02 18:40 ` Stefan Hansson
2026-08-02 18:52 ` Johannes Berg [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=35231759dc9633edf72a745d0079897c000ff5ea.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=newbie13xd@gmail.com \
--cc=newbyte@postmarketos.org \
--cc=phone-devel@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