From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: shuah <shuah@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
mptcp <mptcp@lists.01.org>
Subject: Re: [PATCH] selftests: settings: tests can be in subsubdirs
Date: Mon, 27 Jan 2020 21:34:34 +0100 [thread overview]
Message-ID: <9bb525e5-12a1-9e27-81cd-cf7bc3d5dc2d@tessares.net> (raw)
In-Reply-To: <bcce12e4-f122-10ae-dbc7-cc199d9716b6@kernel.org>
Hi Shuah,
On 27/01/2020 18:16, shuah wrote:
> On 1/27/20 9:05 AM, Matthieu Baerts wrote:
[...]
>> Kees, Thank you for this review!
>>
>> Shuah, I am sorry to send you this new request. It is just to inform
>> you that the first selftests for MPTCP are now in "net-next" repo,
>> ready for the future Linux 5.6.
>> We would then be very happy to see this patch here below for the
>> kselftest framework accepted to avoid timeouts. Locally we apply this
>> patch before running the selftests but we cannot ask everybody running
>> MPTCP' selftests to do the same :)
>>
>>
>
> I am sorry for the delay. My bad. Looks like I just missed it. I will
> make sure it gets into 5.6-rc1
That's alright, thank you for having applied this patch in your "next"
branch!
Cheers,
Matt
--
Matthieu Baerts | R&D Engineer
matthieu.baerts@tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium
prev parent reply other threads:[~2020-01-27 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 17:12 [PATCH] selftests: settings: tests can be in subsubdirs Matthieu Baerts
2019-11-21 16:32 ` Matthieu Baerts
2019-11-21 18:52 ` Kees Cook
2020-01-27 16:05 ` Matthieu Baerts
2020-01-27 17:16 ` shuah
2020-01-27 20:34 ` Matthieu Baerts [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=9bb525e5-12a1-9e27-81cd-cf7bc3d5dc2d@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mptcp@lists.01.org \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).