From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "René van Dorst" <opensource@vdorst.com>
Cc: WireGuard list <wireguard@lists.zx2c4.com>
Subject: Re: general protection fault: 0000 [#1] SMP with latest commit a073ccac17a85f0c453698d0213cc8b86ecc3dfe
Date: Mon, 20 Nov 2017 17:08:37 +0100 [thread overview]
Message-ID: <CAHmME9oxWCdnmBgHHWAEKSz2DHwT7fFPsZmpESABPqCXJY=e6Q@mail.gmail.com> (raw)
In-Reply-To: <20171120160704.Horde.BsfBQSW63FEc1BxXECCXXS4@www.vdorst.com>
Thanks for the report! You'll notice I CCd you in the last email,
hoping you'd find just this. :)
Investigating.
next prev parent reply other threads:[~2017-11-20 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 16:07 René van Dorst
2017-11-20 16:08 ` Jason A. Donenfeld [this message]
2017-11-20 16:19 ` Jason A. Donenfeld
2017-11-20 16:29 ` René van Dorst
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='CAHmME9oxWCdnmBgHHWAEKSz2DHwT7fFPsZmpESABPqCXJY=e6Q@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=opensource@vdorst.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).