From: Pavel Skripkin <paskripkin@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>, "Takashi Iwai" <tiwai@suse.de>
Cc: kvalo@kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, senthilkumar@atheros.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+03110230a11411024147@syzkaller.appspotmail.com,
syzbot+c6dde1f690b60e0b9fbe@syzkaller.appspotmail.com
Subject: Re: [PATCH v5 1/2] ath9k: fix use-after-free in ath9k_hif_usb_rx_cb
Date: Fri, 10 Jun 2022 21:34:11 +0300 [thread overview]
Message-ID: <dabcbe61-5d77-7290-efd5-3fe71ca60640@gmail.com> (raw)
In-Reply-To: <87r13w2wxq.fsf@toke.dk>
[-- Attachment #1.1: Type: text/plain, Size: 562 bytes --]
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?
With regards,
Pavel Skripkin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-06-10 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 21:28 [PATCH v5 1/2] ath9k: fix use-after-free in ath9k_hif_usb_rx_cb Pavel Skripkin
2022-05-21 21:28 ` [PATCH v5 2/2] ath9k: htc: clean up statistics macros Pavel Skripkin
2022-05-22 0:17 ` kernel test robot
2022-05-22 10:07 ` kernel test robot
2022-06-10 12:49 ` [PATCH v5 1/2] ath9k: fix use-after-free in ath9k_hif_usb_rx_cb Takashi Iwai
2022-06-10 18:30 ` Toke Høiland-Jørgensen
2022-06-10 18:34 ` Pavel Skripkin [this message]
2022-06-10 21:02 ` Toke Høiland-Jørgensen
[not found] <20220522041542.2911-1-hdanton@sina.com>
2022-06-10 13:01 ` Pavel Skripkin
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=dabcbe61-5d77-7290-efd5-3fe71ca60640@gmail.com \
--to=paskripkin@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=senthilkumar@atheros.com \
--cc=syzbot+03110230a11411024147@syzkaller.appspotmail.com \
--cc=syzbot+c6dde1f690b60e0b9fbe@syzkaller.appspotmail.com \
--cc=tiwai@suse.de \
--cc=toke@toke.dk \
/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