From: Anh Tuan Phan <tuananhlfc@gmail.com>
To: Ivan Orlov <ivan.orlov0322@gmail.com>
Cc: daniel@iogearbox.net,
linux-kernel-mentees@lists.linuxfoundation.org, ast@kernel.org,
andrii@kernel.org, bpf@vger.kernel.org, martin.lau@linux.dev
Subject: Re: [PATCH v2] samples/bpf: Add more instructions to build dependencies and, configuration in README.rst
Date: Fri, 7 Jul 2023 20:51:18 +0700 [thread overview]
Message-ID: <dc7a79e0-acfa-c65e-d9db-80806758f846@gmail.com> (raw)
In-Reply-To: <4e4a3024-0482-665c-212f-f0084f404239@gmail.com>
Thanks, will do
On 7/7/23 02:43, Ivan Orlov wrote:
> On 06.07.2023 20:00, Anh Tuan Phan wrote:
>> Update the Documentation to mention that some samples require pahole
>> v1.16 and kernel built with CONFIG_DEBUG_INFO_BTF=y
>>
>> Signed-off-by: Anh Tuan Phan <tuananhlfc@gmail.com>
>> ---
>
> Minor nit: you should write what changed since the first version of the
> patch here, otherwise the changes are pretty hard to follow.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2023-07-07 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 16:00 [PATCH v2] samples/bpf: Add more instructions to build dependencies and, configuration in README.rst Anh Tuan Phan
2023-07-06 18:16 ` Stanislav Fomichev via Linux-kernel-mentees
2023-07-07 13:48 ` Anh Tuan Phan
2023-07-07 16:57 ` Stanislav Fomichev via Linux-kernel-mentees
2023-07-09 14:37 ` Anh Tuan Phan
2023-07-09 15:21 ` Khalid Masum
2023-07-09 15:36 ` Siddh Raman Pant
2023-07-10 13:03 ` Anh Tuan Phan
2023-07-11 12:53 ` Siddh Raman Pant
2023-07-10 12:58 ` Anh Tuan Phan
2023-07-10 17:21 ` Stanislav Fomichev via Linux-kernel-mentees
2023-07-06 19:43 ` Ivan Orlov
2023-07-07 13:51 ` Anh Tuan Phan [this message]
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=dc7a79e0-acfa-c65e-d9db-80806758f846@gmail.com \
--to=tuananhlfc@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=martin.lau@linux.dev \
/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