From: Matthew Wilcox <willy@infradead.org>
To: lsf-pc@lists.linux-foundation.org, 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
Subject: [LSF/MM/BPF] Running BOF
Date: Sat, 4 Mar 2023 05:03:53 +0000 [thread overview]
Message-ID: <ZALROVnC+GDXsBne@casper.infradead.org> (raw)
Sunday May 7th is the Vancouver Marathon, and both Josef and I are
registered. As such, neither of us may be feeling much like joining
or leading a run. If anyone else is interested in participating,
https://bmovanmarathon.ca/ offers 8km and 21.1km races as well. If you
just want a spot of morning exercise, I can suggest routes, but will
probably not join you.
For those concerned about how the marathon will affect getting around
Vancouver, you can see the various course maps:
https://bmovanmarathon.ca/marathon#course (8:30am-3pm)
https://bmovanmarathon.ca/halfmarathon#course (7am-11am)
https://bmovanmarathon.ca/8km#course (9:30am - 11am)
Don't expect to walk around Stanley Park until the marathon is over.
The Skytrain from the airport will be largely unaffected (possibly
infested with sweaty runners). Bus routes may have diversions in place,
but the roads will open once runners are no longer using that particular
stretch, so eg Cambie & 49th will reopen to traffic quite early while
Pacific & Georgia will remain closed for much of the day.
If you want to come out & cheer for Josef and/or myself, let us know
and we can suggest good spots.
next reply other threads:[~2023-03-04 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 5:03 Matthew Wilcox [this message]
2023-04-13 18:28 ` [LSF/MM/BPF] Running BOF James Bottomley
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=ZALROVnC+GDXsBne@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 NNTP newsgroup(s).