tpmdd-devel Archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Cc: Linux Security Summit Program Committee
	<lss-pc@lists.linuxfoundation.org>,
	keyrings@linux-nfs.org, gentoo-hardened@gentoo.org,
	kernel-hardening@lists.openwall.com, selinux@vger.kernel.org,
	linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
	Audit-ML <linux-audit@redhat.com>,
	linux-crypto@vger.kernel.org, lwn@lwn.net,
	linux-integrity@vger.kernel.org, fedora-selinux-list@redhat.com
Subject: Re: [tpmdd-devel] [ANNOUNCE][CFP] Linux Security Summit North America 2022
Date: Sat, 19 Mar 2022 09:31:55 +1100 (AEDT)	[thread overview]
Message-ID: <3f2d2915-b2b9-1646-d0e9-192296327633@namei.org> (raw)
In-Reply-To: <3e5acc67-829-fafb-c82-833fc22b35a@namei.org>

On Tue, 8 Feb 2022, James Morris wrote:

>   * Event:                September 23-24

Correction: This should be 23-24 June per the top of the email.


-- 
James Morris
<jmorris@namei.org>



_______________________________________________
tpmdd-devel mailing list
tpmdd-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tpmdd-devel

      reply	other threads:[~2022-03-18 23:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 22:24 [tpmdd-devel] [ANNOUNCE][CFP] Linux Security Summit North America 2022 James Morris
2022-03-18 22:31 ` James Morris [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=3f2d2915-b2b9-1646-d0e9-192296327633@namei.org \
    --to=jmorris@namei.org \
    --cc=fedora-selinux-list@redhat.com \
    --cc=gentoo-hardened@gentoo.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lss-pc@lists.linuxfoundation.org \
    --cc=lwn@lwn.net \
    --cc=selinux@vger.kernel.org \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).