From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <willy@infradead.org>,
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: Re: [LSF/MM/BPF] Running BOF
Date: Thu, 13 Apr 2023 14:28:52 -0400 [thread overview]
Message-ID: <726533b0e5f511678e4f40a768974fa818e9677f.camel@HansenPartnership.com> (raw)
In-Reply-To: <ZALROVnC+GDXsBne@casper.infradead.org>
On Sat, 2023-03-04 at 05:03 +0000, Matthew Wilcox wrote:
> 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 of you who fancy something more scenic and less damaging to
the knees, Mike and I were planning a hike around the chain lakes trail
by Mt Baker:
https://www.fs.usda.gov/recarea/mbs/recarea/?recid=80181
As long as there's been no recent snowfall, both the trail and the
Bagley Lakes trailhead should be accessible. The Rangers have been
known to keep Chain Lakes closed until June, so we might have to go
along one of the other trails instead.
Mike and I are planning to drive up early on Sunday from Seattle, but
it is possible to drive from Vancouver as well if you have a car
(There's a US$5/car charge at the car park).
Regards,
James
prev parent reply other threads:[~2023-04-13 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 5:03 Matthew Wilcox
2023-04-13 18:28 ` James Bottomley [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=726533b0e5f511678e4f40a768974fa818e9677f.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--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 \
--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