BPF List
 help / color / mirror / Atom feed
From: "Daniel Müller" <deso@posteo.net>
To: Mykola Lysenko <mykolal@fb.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"ast@kernel.org" <ast@kernel.org>,
	"andrii@kernel.org" <andrii@kernel.org>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH bpf-next v2 0/3] Maintain selftest configuration in-tree
Date: Tue, 26 Jul 2022 23:59:51 +0000	[thread overview]
Message-ID: <20220726235951.exnt2tfcxe5nxo4a@nuc> (raw)
In-Reply-To: <518BDA5D-DA78-4BD0-8C96-536ADCCC37AA@fb.com>

On Tue, Jul 26, 2022 at 11:14:40PM +0000, Mykola Lysenko wrote:
> Hey Daniel,
> 
> While each patch in series shows v3, the cover latter subject still shows v2, although description shows v2 -> v3 changes. This also explains why CI showed v2 version in PR. Something to check in your setup.

Thanks for pointing that out. Let me resend a clean v4 with correct
cover letter (to prevent any confusion from having two v3 floating
around).

Sorry about that.

[..]

Thanks,
Daniel

  reply	other threads:[~2022-07-27  0:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 20:11 [PATCH bpf-next v2 0/3] Maintain selftest configuration in-tree Daniel Müller
2022-07-26 20:11 ` [PATCH bpf-next v3 1/3] selftests/bpf: Sort configuration Daniel Müller
2022-07-26 20:11 ` [PATCH bpf-next v3 2/3] selftests/bpf: Copy over libbpf configs Daniel Müller
2022-07-26 20:11 ` [PATCH bpf-next v3 3/3] selftests/bpf: Adjust vmtest.sh to use local kernel configuration Daniel Müller
2022-07-26 23:04 ` [PATCH bpf-next v2 0/3] Maintain selftest configuration in-tree Mykola Lysenko
2022-07-26 23:14   ` Mykola Lysenko
2022-07-26 23:59     ` Daniel Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-19 18:02 Daniel Müller
2022-07-22  6:15 ` Martin KaFai Lau

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=20220726235951.exnt2tfcxe5nxo4a@nuc \
    --to=deso@posteo.net \
    --cc=Kernel-team@fb.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=mykolal@fb.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