From: Matthew Wilcox <willy@infradead.org>
To: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
bpf@vger.kernel.org
Cc: lsf-pc@lists.linux-foundation.org
Subject: [LSF/MM/BPF TOPIC] Running BOF
Date: Wed, 17 Apr 2024 18:01:00 +0100 [thread overview]
Message-ID: <ZiAATJkOF-FulDyS@casper.infradead.org> (raw)
As in previous years, I'll be heading out for a run each morning and I'd
be delighted to have company. Assuming our normal start time (breakfast
at 8am, sessions at 9am), I'll aim for a 6:30am start so we can go
for an hour, have half an hour to shower etc, then get to breakfast.
We'll meet just outside the Hilton main lobby on Temple Street.
I don't know Salt Lake City at all. I'll be arriving a few days in
advance, so I'll scout various routes then. It seems inevitable that
we'll head up Ensign Peak one day (6 mile round trip from the Hilton
with 348m of elevation) and probably do something involving City Creek /
Bonneville Boulevard another day. If anyone does know the various trails,
I'd be delighted to listen to your advice.
Running pace will be negotiated by whoever shows up; I'll be tapering for
the Ottawa marathon two weeks later, so I'm not going to be pushing for
a fast pace. This is a social group run, not a training opportunity.
People who want to do more or less are welcome to start with us and
break off as they choose.
You don't need to sign up for this, but if you let me know whether you're
showing up, I might wait a few extra minutes for you if you're late ;-)
next reply other threads:[~2024-04-17 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 17:01 Matthew Wilcox [this message]
2024-05-10 23:35 ` [LSF/MM/BPF TOPIC] Running BOF Matthew Wilcox
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=ZiAATJkOF-FulDyS@casper.infradead.org \
--to=willy@infradead.org \
--cc=bpf@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@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 read-only IMAP folder(s) and NNTP newsgroup(s).