From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Shuah Khan <shuah@kernel.org>,
WireGuard mailing list <wireguard@lists.zx2c4.com>,
Netdev <netdev@vger.kernel.org>,
linux-kselftest@vger.kernel.org,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wireguard: selftests: update config fragments
Date: Tue, 26 Jul 2022 15:06:09 +0200 [thread overview]
Message-ID: <CAHmME9ogBc_uX_TutV7ZC=nmhhZEtKLA3ezyx4VFwotietNytQ@mail.gmail.com> (raw)
In-Reply-To: <20220726130058.21833-1-lukas.bulwahn@gmail.com>
Hi Lukas,
Thanks for researching this! I'll apply this to my wireguard tree and
send it up to netdev during my next push.
https://git.zx2c4.com/wireguard-linux/commit/?id=6da997932c4d4cb41c4a35d5541d0e4e1154fdb7
Jason
prev parent reply other threads:[~2022-07-26 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 13:00 Lukas Bulwahn
2022-07-26 13:06 ` Jason A. Donenfeld [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='CAHmME9ogBc_uX_TutV7ZC=nmhhZEtKLA3ezyx4VFwotietNytQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).