From: Kees Cook <keescook@chromium.org>
To: linux-hardening@vger.kernel.org
Subject: KSPP Meeting: Wed 10am US Pacific
Date: Tue, 7 Feb 2023 15:09:23 -0800 [thread overview]
Message-ID: <63e2da23.170a0220.e2c26.064b@mx.google.com> (raw)
Hello,
Here's the reminder for the KSPP meeting, held every 2 weeks.
VC link: https://meet.google.com/grn-oshi-cpq
Calendar: https://calendar.google.com/calendar/u/0/embed?src=47005f8f50f21da6133d7239f3cb93d1624d2e1949963ea75dd86d5f2d5721e0@group.calendar.google.com
See folks there!
-Kees
--
Kees Cook
reply other threads:[~2023-02-07 23:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=63e2da23.170a0220.e2c26.064b@mx.google.com \
--to=keescook@chromium.org \
--cc=linux-hardening@vger.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