From: Joao Martins <joao.m.martins@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvme@vger.kernel.org" <linux-nvme@vger.kernel.org>
Subject: Re: [LSFMMBPF 2021] A status update
Date: Tue, 5 Jan 2021 20:30:26 +0000 [thread overview]
Message-ID: <0b356707-1ad1-a147-cd5e-224a1a8658a0@oracle.com> (raw)
In-Reply-To: <20201212172957.GE2443@casper.infradead.org>
On 12/12/20 5:29 PM, Matthew Wilcox wrote:
> And most urgently, when should we have the GUP meeting? On the call,
> I suggested Friday the 8th of January, but I'm happy to set something
> up for next week if we'd like to talk more urgently. Please propose a
> date & time. I know we have people in Portugal and Nova Scotia who need
> to be involved live, so a time friendly to UTC+0 and UTC-4 would be good.
FWIW, I would suggest the same time as you had for PageFolio (18h GMT / 10pm PT / 13h ET)
given it can cover many tz in a not-so-bothersome time.
But instead of Jan 8 perhaps better for next week (Jan 15) in case folks
are still in new year holidays (given we are in the first week of the year).
Joao
prev parent reply other threads:[~2021-01-05 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 15:48 Josef Bacik
2020-12-12 17:29 ` Matthew Wilcox
2020-12-15 12:23 ` Michal Hocko
2020-12-15 13:43 ` Hannes Reinecke
2021-01-05 20:30 ` Joao Martins [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=0b356707-1ad1-a147-cd5e-224a1a8658a0@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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