mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yuran Pereira <yuran.pereira@hotmail.com>
To: Kui-Feng Lee <sinquersw@gmail.com>
Cc: bpf@vger.kernel.org, yonghong.song@linux.dev, shuah@kernel.org,
	ast@kernel.org, daniel@iogearbox.net, song@kernel.org,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
	haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
	brauner@kernel.org, iii@linux.ibm.com, kuifeng@meta.com,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] selftests/bpf: Replaces CHECK macros and adds malloc failure checks to bpf_iter
Date: Sat, 28 Oct 2023 06:46:06 +0530	[thread overview]
Message-ID: <DB3PR10MB683516C89C063FEC4D94D45BE8A3A@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <563d1ae7-8d1f-48d5-b742-989ce482c4f1@gmail.com>

On Wed, Oct 25, 2023 at 09:37:44PM -0700, Kui-Feng Lee wrote:
> 
> 
> On 10/25/23 19:03, Yuran Pereira wrote:
> > This patch series contains the following updates:
> > - Replaces the usage of all the CHECK macros in bpf_iter
> >    to the appropriate ASSERT_* macro calls
> > - Adds appropriate malloc failure checks to bpf_iter
> > 
> > Changes in v2:
> > - Removed unused "duration" variable which caused compilation error
> >    as reported by Yonghong Song [1]
> > - Improved malloc failure handling as suggested by Kui-Feng Lee [2]
> > - Ensured propper patch formatting (i.e. sending it as a set instead
> >    of two distinct patches)
> > 
> > [1] https://lore.kernel.org/lkml/3531360b-c933-4c5f-a84c-17edf0592519@linux.dev/
> > [2] https://lore.kernel.org/lkml/7d703c4c-1a24-4806-a483-c02efb666059@gmail.com
> > 
> > 
> > Previous version:
> > v1 - https://lore.kernel.org/lkml/DB3PR10MB683589A5F705C6CA5BE0D325E8DFA@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM
> >     - https://lore.kernel.org/lkml/DB3PR10MB68356D7CDF6005480BE5876CE8DEA@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM
> > 
> > Yuran Pereira (2):
> >    selftests/bpf: Convert CHECK macros to ASSERT_* macros in bpf_iter
> >    selftests/bpf: Add malloc failure checks in bpf_iter
> > 
> >   .../selftests/bpf/prog_tests/bpf_iter.c       | 88 +++++++++----------
> >   1 file changed, 44 insertions(+), 44 deletions(-)
> > 
> 
> 
> For the cover letter, you can just put it at the same directory of
> patch 1 and 2 and sent them with "git send-email" at once. All of them
> will be in the same thread.
> 
> "git format-patch --cover-letter ..." will generate a template
> of the cover letter along with patches. FYI
>
Hello Kui-Feng, thanks for the feedback.

So I did use "git format-patch --cover-letter", but for some reason
"git send-email /path-to-patches/" seems to be deliberately sending
the cover letter on a separate thread. IDK why.

But "git send-email --compose" seems to be working as expected, so
I'll use that and manually copy the cover letter generated by
format-patch to ensure it's all on the same thread.

Since I already butchered this thread, I will send v3 series on a 
separate thread. But I'll ensure to reference this thread on the 
cover letter.

I'll be more careful with future patches.

      reply	other threads:[~2023-10-28  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  2:03 Yuran Pereira
2023-10-26  4:37 ` Kui-Feng Lee
2023-10-28  1:16   ` Yuran Pereira [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=DB3PR10MB683516C89C063FEC4D94D45BE8A3A@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM \
    --to=yuran.pereira@hotmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=iii@linux.ibm.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuifeng@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mykolal@fb.com \
    --cc=sdf@google.com \
    --cc=shuah@kernel.org \
    --cc=sinquersw@gmail.com \
    --cc=song@kernel.org \
    --cc=yonghong.song@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

all inboxes | Powered by JetHome®