linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
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
Subject: Re: Scheduling conflicts
Date: Tue, 30 Apr 2019 06:11:20 -0400	[thread overview]
Message-ID: <20190430101120.GD3715@dhcp22.suse.cz> (raw)
In-Reply-To: <20190429235440.GA13796@bombadil.infradead.org>

On Mon 29-04-19 16:54:41, Matthew Wilcox wrote:
> On Thu, Apr 25, 2019 at 02:03:34PM -0600, 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
> 
> The schedule continues to evolve ... I would very much like to have
> Christoph Hellwig in the room for the Eliminating Tail Pages discussion,
> but he's now scheduled to speak in a session at the same time (16:00
> Tuesday).  I assume there'll be time for agenda-bashing at 9am tomorrow?

I have swapped slots at 16:00 and 16:30 so there shouldn't be any
conflict now. Let me know if that doesn't fit.

-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2019-04-30 10:11 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   ` [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Vlastimil Babka
2019-04-29 10:46     ` 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 [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=20190430101120.GD3715@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --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=willy@infradead.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).