[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wmqwahoj.fsf@kernel.org>
Date: Thu, 22 Feb 2024 12:59:08 +0200
From: Kalle Valo <kvalo@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Jeff Johnson <quic_jjohnson@...cinc.com>, Karthikeyan Periyasamy
<quic_periyasa@...cinc.com>, <netdev@...r.kernel.org>,
<linux-wireless@...r.kernel.org>
Subject: Re: pull-request: wireless-next-2024-02-20
Kalle Valo <kvalo@...nel.org> writes:
> Jakub Kicinski <kuba@...nel.org> writes:
>
>> On Wed, 21 Feb 2024 17:18:41 -0800 Jeff Johnson wrote:
>>> > definitely a flaw in 6db6e70a17f6 ("wifi: ath12k: Introduce the
>>> > container for mac80211 hw")
>>> >
>>> > my setup is using gcc which isn't flagging this :(
>>> >
>>> > Karthikeyan, can you submit a patch?
>>>
>>> I see this was already fixed by:
>>> 04edb5dc68f4 ("wifi: ath12k: Fix uninitialized use of ret in
>>> ath12k_mac_allocate()")
>>
>> In wireless-next? Could you do a quick follow up PR so that
>> it gets into net-next before the warning propagates into more
>> of the networking sub-trees?
>
> The fix is in ath-next but I'll pull ath-next into wireless-next and
> then send a wireless-next pull request. So you should have the pull
> request in few hours.
The pull request is sent:
https://patchwork.kernel.org/project/netdevbpf/patch/20240222105205.CEC54C433F1@smtp.kernel.org/
Of course the ath patches haven't been in linux-next yet so let's hope
that we are not introducing new problems. We need to add ath-next into
linux-next to catch problems as early as possible.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists