From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sreevani Sreejith <ssreevani@meta.com>
Cc: void@manifault.com, psreep@gmail.com,
Linux BPF <bpf@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
andrii@kernel.org, mykola@meta.com,
Linux Documentation <linux-doc@vger.kernel.org>
Subject: Re: [PATCH V2 bpf-next] BPF, docs: libbpf Overview Document
Date: Sat, 11 Mar 2023 09:14:10 +0700 [thread overview]
Message-ID: <ZAvj8q1C1vhGX4kT@debian.me> (raw)
In-Reply-To: <DM4PR15MB53548D70925C64EE3CEF8F86CABA9@DM4PR15MB5354.namprd15.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Fri, Mar 10, 2023 at 04:11:38PM +0000, Sreevani Sreejith wrote:
> Thanks, Sanjaya, for taking the time to review. I will submit a patch with all the changes you suggested. I left the emphasis on the code line as is. If you have a strong suggestion to remove it, let me know.
>
> Also, this is the first time I am sending a reply to a patch. So please let me know if I have to adjust the reply format.
>
Hi,
It seems like you reply with HTML format, which makes plain-text
formatting looks messy. See Documentation/process/email-clients.rst for
how to configure your email client to send plain-text emails.
Also, please reply inline with appropriate context while keeping list of
recipients in To: and Cc: intact (via "Reply all" button in your
client). I have to add original recipients back since these are omitted
from your reply.
Thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2023-03-11 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM4PR15MB53548D70925C64EE3CEF8F86CABA9@DM4PR15MB5354.namprd15.prod.outlook.com>
2023-03-11 2:14 ` Bagas Sanjaya [this message]
2023-03-09 22:49 [PATCH V2 bpf-next] BPF, docs: libbpf Overview Document Sreevani Sreejith
2023-03-10 4:35 ` Bagas Sanjaya
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=ZAvj8q1C1vhGX4kT@debian.me \
--to=bagasdotme@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mykola@meta.com \
--cc=psreep@gmail.com \
--cc=ssreevani@meta.com \
--cc=void@manifault.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