From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Looks like 4.13 introduces a new incompatibility
Date: Sun, 9 Jul 2017 22:17:44 -0500 [thread overview]
Message-ID: <20170710031744.GA18054@wolff.to> (raw)
In-Reply-To: <CAHmME9pbky9H=+QkXA2VMeZ3OQonxxZ_H2-Jiz8Gy6FeYuR+7g@mail.gmail.com>
On Mon, Jul 10, 2017 at 05:03:42 +0200,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>
>I need to annoy Ted Tso about this. It'll get merged for rc1 or rc2.
OK. I'll confirm when it builds again. I might try it out early if Tso
has it in a public develoment tree before it gets to Linus' tree. This
might show up other issues in things that build after cookie.o and so might
be worthwhile even if building kernels from source is otherwise not usually
worth the effort for me.
next prev parent reply other threads:[~2017-07-10 3:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 1:48 Bruno Wolff III
2017-07-10 2:01 ` Jason A. Donenfeld
2017-07-10 2:56 ` Bruno Wolff III
2017-07-10 3:03 ` Jason A. Donenfeld
2017-07-10 3:17 ` Bruno Wolff III [this message]
2017-07-10 3:26 ` Jason A. Donenfeld
2017-07-10 5:44 ` Bruno Wolff III
2017-07-15 21:57 ` Bruno Wolff III
2017-07-15 22:22 ` Jason A. Donenfeld
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=20170710031744.GA18054@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.com \
--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).