From: "Benjamin Coddington" <bcodding@redhat.com>
To: "Matthew Wilcox" <willy@infradead.org>
Cc: lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: LSF/MM/BPF 2022: Running BOF
Date: Fri, 22 Apr 2022 07:43:08 -0400 [thread overview]
Message-ID: <15847F8A-5246-4634-ABBE-9C05AA3CBF34@redhat.com> (raw)
In-Reply-To: <Yl7TUDtLcrhXcp1g@casper.infradead.org>
On 19 Apr 2022, at 11:20, Matthew Wilcox wrote:
> As in the past few years, let's hold a running BOF.
>
> I propose meeting in the lobby of the Margaritaville hotel at 6:15 for
> a 6:30 departure for an hour-long run on Monday, Tuesday and Wednesday
> mornings. I'm assuming breakfast will be 8-9am and sessions start at 9am.
> Pace will be determined by whoever shows up.
>
> We're only a mile from the North Lykken north Trailhead.
> Other trails are a little more distant. I've been reading
> http://www.hiking-in-ps.com/the-north-lykken-trail/ (note this map is
> for the south trailhead of the North Lykken trail). I haven't been
> to this area in 30 years and I have no idea what the trails are like,
> so if somebody has local information, that would be great.
>
> I note that the room rate includes complimentary bicycle rentals. If
> we want to, we could cycle to various other local trails.
I'm in unless I'm trying to run in the PM. I've got a tentative run/explore
of one of the slot canyons about an hour away if I can swing it (painted
canyon, ladder canyon, I may have to borrow a car from someone), and would
be nice to try to get up into Mt San Jacinto park as well.
I'm interested in getting some trail and elevation, but I've not run out
there yet and will need to scope out what's possible when I get there.
Ben
prev parent reply other threads:[~2022-04-22 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 15:20 Matthew Wilcox
2022-04-22 11:43 ` Benjamin Coddington [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=15847F8A-5246-4634-ABBE-9C05AA3CBF34@redhat.com \
--to=bcodding@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.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