[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiPQ8PTWZuWXw8s+OLNmgXSM3+DxmY=uKd4F-Nnu4TB9A@mail.gmail.com>
Date: Tue, 4 Feb 2025 11:06:57 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] kthreads fixes for v6.14-rc2
On Tue, 4 Feb 2025 at 10:58, Frederic Weisbecker <frederic@...nel.org> wrote:
>
> - Properly handle return value when allocation fails for the preferred
> affinity.
Well, we have exactly one caller of this function, and that caller
doesn't actually care about the return value.
The function is literally the "preferred" affinity. If the affinity
setup fails, it's harmless.
Anyway, the fix doesn't look wrong, and I've pulled it, but it's just
all very harmless. I think the "set but not used" error could have
been fixed by just removing the 'ret' variable entirely.
Linus
Powered by blists - more mailing lists