From: Greg KH <gregkh@linuxfoundation.org>
To: 20230801155823.206985-1-ghandatmanas@gmail.com
Cc: Linux-kernel-mentees@lists.linuxfoundation.org,
syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com,
salah.triki@gmail.com, linux-kernel@vger.kernel.org,
luisbg@kernel.org
Subject: Re: Ping
Date: Sun, 13 Aug 2023 08:25:17 +0200 [thread overview]
Message-ID: <2023081356-grew-passage-e17c@gregkh> (raw)
In-Reply-To: <301364dc-9709-8c8e-6881-66863cb3d29b@gmail.com>
On Sun, Aug 13, 2023 at 11:48:29AM +0530, Manas Ghandat wrote:
> Just a friendly ping to the patch :)
There was no context here at all as to what patch you are responding to :(
_______________________________________________
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:[~2023-08-13 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 6:18 Ping Manas Ghandat
2023-08-13 6:25 ` Greg KH [this message]
2023-08-13 7:50 ` Ping Willy Tarreau
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=2023081356-grew-passage-e17c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=20230801155823.206985-1-ghandatmanas@gmail.com \
--cc=Linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@kernel.org \
--cc=salah.triki@gmail.com \
--cc=syzbot+fc26c366038b54261e53@syzkaller.appspotmail.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