[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <878rq42pwz.fsf@toke.dk>
Date: Fri, 10 Jun 2022 23:02:04 +0200
From: Toke Høiland-Jørgensen <toke@...e.dk>
To: Pavel Skripkin <paskripkin@...il.com>, Takashi Iwai <tiwai@...e.de>
Cc: kvalo@...nel.org, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, senthilkumar@...eros.com,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
syzbot+03110230a11411024147@...kaller.appspotmail.com,
syzbot+c6dde1f690b60e0b9fbe@...kaller.appspotmail.com
Subject: Re: [PATCH v5 1/2] ath9k: fix use-after-free in ath9k_hif_usb_rx_cb
Pavel Skripkin <paskripkin@...il.com> writes:
> Hi Toke,
>
> On 6/10/22 21:30, Toke Høiland-Jørgensen wrote:
>>
>> In general, if a patch is marked as "changes requested", the right thing
>> to do is to bug the submitter to resubmit. Which I guess you just did,
>> so hopefully we'll get an update soon :)
>>
>
>
> I agree here. The build fix is trivial, I just wanted to reply to
> Hillf like 2 weeks ago, but an email got lost in my inbox.
>
> So, i don't know what is correct thing to do rn: wait for Hillf's
> reply or to quickly respin with build error addressed?
Up to you. If you respin it now we can just let it sit in patchwork over
the weekend and see if it attracts any further comment; or you can wait
and respin on Monday...
-Toke
Powered by blists - more mailing lists