From: Siddh Raman Pant via Linux-kernel-mentees <linux-kernel-mentees@lists.linuxfoundation.org>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel-mentees
<linux-kernel-mentees@lists.linuxfoundation.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: Ping: [PATCH] net: Fix UAF in ieee80211_scan_rx()
Date: Thu, 07 Jul 2022 17:29:40 +0530 [thread overview]
Message-ID: <181d887b398.167dab1d11045.9186448565104273580@siddh.me> (raw)
In-Reply-To: <YsbIoB5KTqdRva6g@kroah.com>
On Thu, 07 Jul 2022 17:20:56 +0530 Greg KH <gregkh@linuxfoundation.org> wrote
> On Thu, Jul 07, 2022 at 05:06:35PM +0530, Siddh Raman Pant via Linux-kernel-mentees wrote:
> > Ping?
>
> context-less pings, on a patch that was sent less than 1 week ago, are
> usually not a good idea. Normally wait for 2 weeks and then resend if
> you have not heard anything back.
>
> good luck!
>
> greg k-h
Sorry, I never intended to disturb anyone.
Thanks for informing,
Siddh
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2022-07-07 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 14:54 [PATCH] net: Fix UAF in ieee80211_scan_rx() Siddh Raman Pant
2022-07-07 11:36 ` Ping: " Siddh Raman Pant via Linux-kernel-mentees
2022-07-07 11:50 ` Greg KH
2022-07-07 11:59 ` Siddh Raman Pant via Linux-kernel-mentees [this message]
2022-07-26 9:55 ` Kalle Valo
2022-07-26 11:50 ` Siddh Raman Pant via Linux-kernel-mentees
2022-07-26 10:07 ` Eric Dumazet via Linux-kernel-mentees
2022-07-26 12:16 ` Siddh Raman Pant via Linux-kernel-mentees
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=181d887b398.167dab1d11045.9186448565104273580@siddh.me \
--to=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=code@siddh.me \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).