From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Michael Halcrow <mhalcrow@google.com>,
David Howells <dhowells@redhat.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Inline encryption support for block devices
Date: Tue, 24 Jan 2017 15:16:14 -0800 [thread overview]
Message-ID: <1485299774.2426.79.camel@HansenPartnership.com> (raw)
In-Reply-To: <CA+POJK0axH9Q87Cq4j6rucKXAKY_8LEQJ6m51+FJmAAA_qxhyA@mail.gmail.com>
On Tue, 2017-01-24 at 14:55 -0800, Michael Halcrow via Lsf-pc wrote:
> Note that I also have a CFP proposal submitted through the web site
> pending.
I don't believe you do. We don't have a web based submissions system;
it's all done by email as the CFP says:
http://marc.info/?l=linux-fsdevel&m=148285919408577
James
next prev parent reply other threads:[~2017-01-24 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 17:32 [LSF/MM TOPIC] Inline encryption support for block devices Theodore Ts'o
2017-01-06 22:29 ` David Howells
2017-01-24 22:55 ` Michael Halcrow
2017-01-24 23:16 ` James Bottomley [this message]
2017-01-12 13:36 ` Lukas Czerner
2017-01-12 16:58 ` Theodore Ts'o
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=1485299774.2426.79.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhalcrow@google.com \
--cc=tytso@mit.edu \
/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).