linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	inux-fsdevel@vger.kernel.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Network Development <netdev@vger.kernel.org>,
	linux-block@vger.kernel.org
Subject: Re: Maintainers / Kernel Summit 2020 planning kick-off
Date: Wed, 1 Jul 2020 09:12:31 +1000	[thread overview]
Message-ID: <CAPM=9tz3heu1-xTyYDA4huszt3LLgF87pKcifc+OCFqJv-KWdA@mail.gmail.com> (raw)
In-Reply-To: <20200515163956.GA2158595@mit.edu>

On Sat, 16 May 2020 at 02:41, Theodore Y. Ts'o <tytso@mit.edu> wrote:
>
> [ Feel free to forward this to other Linux kernel mailing lists as
>   appropriate -- Ted ]
>
> This year, the Maintainers and Kernel Summit will NOT be held in
> Halifax, August 25 -- 28th, as a result of the COVID-19 pandemic.
> Instead, we will be pursuing a virtual conference format for both the
> Maintainers and Kernel Summit, around the last week of August.
>
> As in previous years, the Maintainers Summit is invite-only, where the
> primary focus will be process issues around Linux Kernel Development.
> It will be limited to 30 invitees and a handful of sponsored
> attendees.

What timezone are the conferences being held in? It impacts on what I
can attend quite heavily :-)

Dave.

  parent reply	other threads:[~2020-06-30 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 16:39 Maintainers / Kernel Summit 2020 planning kick-off Theodore Y. Ts'o
2020-05-19  2:42 ` Frank Rowand
2020-06-30 23:12 ` Dave Airlie [this message]
2020-07-01 14:13   ` Theodore Y. 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='CAPM=9tz3heu1-xTyYDA4huszt3LLgF87pKcifc+OCFqJv-KWdA@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=inux-fsdevel@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --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).