From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] Squash to "selftests: bpf: add MPTCP test base"
Date: Wed, 27 Apr 2022 10:33:28 -0700 (PDT) [thread overview]
Message-ID: <1c8d39c9-647b-44a-b4fa-729a2b4decf@linux.intel.com> (raw)
In-Reply-To: <edebd64f-9b82-c4c1-1d03-e39270bf5c58@tessares.net>
On Wed, 27 Apr 2022, Matthieu Baerts wrote:
> Hi Geliang,
>
> Thank you for the patch!
>
> On 27/04/2022 03:28, Geliang Tang wrote:
>> Add CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC as Mat suggested.
>
> Mat's second reply on...
>
> Squash to "selftests: bpf: test bpf_skc_to_mptcp_sock"
>
> ...patch confuses me but I think he meant: we need this patch as it is
> and that's why it is marked as Queued on Patchwork. But for this fix
> here, it is probably best to have a dedicated patch and not a Squash-to
> one because these two config should have been added before as they are
> needed by other BPF selftests.
>
> Did I misunderstand?
>
You understood correctly, Mattheiu. If I send a v2 of the bpf-next patches
today I will add the commit and also queue it in our patchwork.
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-04-27 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 1:28 [PATCH mptcp-next] Squash to "selftests: bpf: add MPTCP test base" Geliang Tang
2022-04-27 2:58 ` Squash to "selftests: bpf: add MPTCP test base": Tests Results MPTCP CI
2022-04-27 10:09 ` [PATCH mptcp-next] Squash to "selftests: bpf: add MPTCP test base" Matthieu Baerts
2022-04-27 17:33 ` Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-07 6:17 Geliang Tang
2022-05-09 11:53 ` Matthieu Baerts
2022-03-31 8:14 Geliang Tang
2022-03-31 13:26 ` Matthieu Baerts
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=1c8d39c9-647b-44a-b4fa-729a2b4decf@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=geliang.tang@suse.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.