All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>, Jerome Glisse <jglisse@redhat.com>,
	lsf-pc@lists.linux-foundation.org, 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: Mon, 29 Apr 2019 06:46:47 -0400	[thread overview]
Message-ID: <yq1v9yx2inc.fsf@oracle.com> (raw)
In-Reply-To: <503ba1f9-ad78-561a-9614-1dcb139439a6@suse.cz> (Vlastimil Babka's message of "Sat, 27 Apr 2019 17:55:20 +0200")


Vlastimil,

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

Yes.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2019-04-29 10:47 UTC|newest]

Thread overview: 17+ 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   ` [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Vlastimil Babka
2019-04-29 10:46     ` Martin K. Petersen [this message]
2019-04-29 11:31       ` [Lsf] " James Bottomley
2019-04-29 11:31         ` James Bottomley
2019-04-29 11:36         ` Martin K. Petersen
2019-04-29 12:17           ` James Bottomley
2019-04-29 12:17             ` James Bottomley
2019-04-29 12:31             ` Martin K. Petersen
2019-04-30 16:03           ` Jonathan Adams
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=yq1v9yx2inc.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --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 \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.