From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
fuse-devel <fuse-devel@lists.linux.dev>,
fstests <fstests@vger.kernel.org>
Subject: Re: Farewell!
Date: Sat, 17 Oct 2026 08:58:31 +0200 [thread overview]
Message-ID: <atMb74jop2vrPJxv@nidhogg.toxiclabs.cc> (raw)
In-Reply-To: <20261016160037.GA107919@frogsfrogsfrogs>
On Fri, Oct 16, 2026 at 09:00:37AM -0700, Darrick J. Wong wrote:
> Hi everyone,
>
> After 14 years at Oracle and 23 years working on Linux, I've decided to
> take an extended break. Today, October 16th, 2026, is my last day.
>
> I don't have any immediate plans to drop the djwong@kernel.org
> forwarding, though ultimately that's up to the sysadmins to decide.
>
> I have very much enjoyed working with you all, and I'm proud of what
> we've accomplished together. Good luck!
Please make sure to always carry your towel and have a pack of salted
peanuts with you...
So long and thank you for all the fish my friend.
>
> --Darrick
>
next prev parent reply other threads:[~2026-10-17 6:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 16:00 Farewell! Darrick J. Wong
2026-10-16 16:23 ` Farewell! Lorenzo Stoakes (ARM)
2026-10-16 17:20 ` Farewell! Bernd Schubert
2026-10-16 19:07 ` Farewell! Brian Foster
2026-10-16 20:21 ` Farewell! Jonathan Corbet
2026-10-16 22:10 ` Farewell! Zorro Lang
2026-10-17 6:58 ` Carlos Maiolino [this message]
2026-10-17 13:47 ` Farewell! Gao Xiang
2026-10-19 0:39 ` Farewell! Darrick J. Wong
2026-10-19 11:42 ` Farewell! Pankaj Raghav (Samsung)
2026-10-19 15:32 ` Farewell! Andrey Albershteyn
2026-10-20 6:33 ` Farewell! Hans Holmberg
2026-10-22 23:39 ` Farewell! Ritesh Harjani
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=atMb74jop2vrPJxv@nidhogg.toxiclabs.cc \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=fuse-devel@lists.linux.dev \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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