linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Jens Axboe <axboe@kernel.dk>, Jerome Glisse <jglisse@redhat.com>,
	lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	lsf@lists.linux-foundation.org
Subject: Re: [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ?
Date: Sat, 27 Apr 2019 17:55:20 +0200	[thread overview]
Message-ID: <503ba1f9-ad78-561a-9614-1dcb139439a6@suse.cz> (raw)
In-Reply-To: <83fda245-849a-70cc-dde0-5c451938ee97@kernel.dk>

On 4/25/19 10:03 PM, Jens Axboe wrote:
> On 4/25/19 2:00 PM, Jerome Glisse wrote:
>> Did i miss preliminary agenda somewhere ? In previous year i think
>> there use to be one by now :)
> 
> You should have received an email from LF this morning with a subject
> of:
> 
> LSFMM 2019: 8 Things to Know Before You Arrive!
> 
> which also includes a link to the schedule. Here it is:
> 
> https://docs.google.com/spreadsheets/d/1Z1pDL-XeUT1ZwMWrBL8T8q3vtSqZpLPgF3Bzu_jejfk

In previous years years there also used to be an attendee list, which is
now an empty tab. Is that intentional due to GDPR?

Thanks,
Vlastimil

  parent reply	other threads:[~2019-04-27 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 20:00 [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Jerome Glisse
2019-04-25 20:03 ` Jens Axboe
2019-04-25 21:19   ` [LSF/MM TOPIC] Lightning round? Theodore Ts'o
2019-04-26  2:39     ` Jens Axboe
2019-04-26  5:20     ` Michal Hocko
2019-04-27 15:55   ` Vlastimil Babka [this message]
2019-04-29 10:46     ` [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Martin K. Petersen
2019-04-29 11:31       ` [Lsf] " James Bottomley
2019-04-29 11:36         ` Martin K. Petersen
2019-04-29 12:17           ` James Bottomley
2019-04-29 12:31             ` Martin K. Petersen
2019-04-30 16:03           ` Jonathan Adams
2019-04-29 23:54   ` Scheduling conflicts Matthew Wilcox
2019-04-30 10:11     ` Michal Hocko

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=503ba1f9-ad78-561a-9614-1dcb139439a6@suse.cz \
    --to=vbabka@suse.cz \
    --cc=axboe@kernel.dk \
    --cc=jglisse@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lsf@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).