From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TALK] WireGuard: Next-Generation Secure Kernel Network Tunnel
Date: Mon, 24 Sep 2018 03:55:06 +0200 [thread overview]
Message-ID: <CAHmME9rjhwpOvC=oyeUCpJ6Ahexq6XJQo6-H8D4xQCb6Uerw_A@mail.gmail.com> (raw)
In-Reply-To: <1537748495.15095.4.camel@HansenPartnership.com>
On Mon, Sep 24, 2018 at 2:21 AM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> On Mon, 2018-09-24 at 02:12 +0200, Jason A. Donenfeld wrote:
> > Confusingly, this talk was actually accepted for the main refereed
> > track at Plumbers, which probably makes more sense anyway for it. So
> > I should probably retract this submission.
> >
> > However, the more important and relevant talk -- the one on Zinc --
> > is really quite appropriate for the kernel track and is sure to spur
> > a lot of needed discussion. So please focus attention on that
> > instead.
>
> Just so you know, this is the only email on the ksummit discuss list
> I've seen from you ... there isn't one proposing either zinc or
> wireguard as a tech topic.
>
> The list archive also only sees this email from you:
>
> https://lists.linuxfoundation.org/pipermail/ksummit-discuss/
>
> so there may be an issue with your outgoing server.
Yikes! However, I'm certain it's not my outgoing server. My mail
server logs show that lists.linuxfoundation.org replied with the
following IDs for each of the two messages:
- 250 2.0.0 Ok: queued as AC122174
- 250 2.0.0 Ok: queued as 8EF1AF8
The one I sent earlier today following up gave a similar response:
- 250 2.0.0 Ok: queued as 63A72180
I'm adding Konstantin to the CC to see what's up.
next prev parent reply other threads:[~2018-09-24 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHmME9oVReKvhpm1CSnF3KLDYtt63SvauHXZ-m6mWR=zno2OJA@mail.gmail.com>
2018-09-24 0:12 ` Jason A. Donenfeld
2018-09-24 0:21 ` James Bottomley
2018-09-24 1:55 ` Jason A. Donenfeld [this message]
[not found] ` <CAHmME9rRnPydFT0CVugiEkVhjHsGukruYqcfdiHu1sSU40A9bQ@mail.gmail.com>
2018-09-24 1:57 ` [Ksummit-discuss] Fwd: [TECH TALK] Zinc: Minimal Light-weight Kernel Cryptography API 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='CAHmME9rjhwpOvC=oyeUCpJ6Ahexq6XJQo6-H8D4xQCb6Uerw_A@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.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