mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] maintainers: update my email address
Date: Fri, 8 Jan 2021 22:46:02 -0800	[thread overview]
Message-ID: <20210109064602.GU6918@magnolia> (raw)

From: Darrick J. Wong <darrick.wong@oracle.com>

Change my email contact ahead of a likely painful eleven-month migration
to a certain cobalt enteprisey groupware cloud product that will totally
break my workflow.  Some day I may get used to having to email being
sequestered behind both claret and cerulean oath2+sms 2fa layers, but
for now I'll stick with keying in one password to receive an email vs.
the required four.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
 MAINTAINERS |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 6eff4f720c72..9ed3ec2aa1aa 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9273,7 +9273,7 @@ F:	drivers/net/ethernet/sgi/ioc3-eth.c
 
 IOMAP FILESYSTEM LIBRARY
 M:	Christoph Hellwig <hch@infradead.org>
-M:	Darrick J. Wong <darrick.wong@oracle.com>
+M:	Darrick J. Wong <djwong@kernel.org>
 M:	linux-xfs@vger.kernel.org
 M:	linux-fsdevel@vger.kernel.org
 L:	linux-xfs@vger.kernel.org
@@ -19505,7 +19505,7 @@ F:	arch/x86/xen/*swiotlb*
 F:	drivers/xen/*swiotlb*
 
 XFS FILESYSTEM
-M:	Darrick J. Wong <darrick.wong@oracle.com>
+M:	Darrick J. Wong <djwong@kernel.org>
 M:	linux-xfs@vger.kernel.org
 L:	linux-xfs@vger.kernel.org
 S:	Supported

             reply	other threads:[~2021-01-09  6:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09  6:46 Darrick J. Wong [this message]
2021-01-09 19:00 ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2026-07-21  8:23 [PATCH] MAINTAINERS: " Roger Pau Monne
2026-07-21 11:58 ` Juergen Gross
2026-07-21 12:24 ` Jens Axboe
2025-11-18 12:18 Bartosz Golaszewski
2025-11-19 11:03 ` Bartosz Golaszewski
2024-02-01  2:10 [PATCH] MAINTAINERS: Update " Leo Yan
2023-10-08 10:58 [PATCH] MAINTAINERS: update " Ondřej Jirman
2021-09-20  7:28 Bartosz Golaszewski
2021-09-20  9:42 ` Andy Shevchenko
2021-09-20 11:41   ` Bartosz Golaszewski
2021-09-23 21:50 ` Linus Walleij
2021-09-29 21:01 ` Wolfram Sang
2021-09-30  7:17   ` Bartosz Golaszewski
2020-10-05 16:45 Antoine Tenart
2020-01-22 10:18 [PATCH] MAINTAINERS: Update " Andrew Murray
2020-01-22 10:53 ` Lorenzo Pieralisi
2019-12-09  9:39 [PATCH] MAINTAINERS: update " lukasz.luba
2019-12-09 17:53 ` Krzysztof Kozlowski
2019-12-10  9:46   ` Lukasz Luba
2019-07-17 10:32 [PATCH] MAINTAINERS: Update " Julien Thierry
2019-07-17 11:36 ` Marc Zyngier
2019-07-17 11:43 ` Will Deacon
2018-12-03 10:23 Boris Brezillon
2018-04-04 12:03 [PATCH] MAINTAINERS: update " Bernat, Yehezkel
2018-04-05 10:28 ` Mika Westerberg
2017-02-03 11:18 Amit Shah
2017-02-03 15:11 ` Michael S. Tsirkin
2017-02-03 15:34   ` Amit Shah
2012-03-06  0:58 Stephen Warren
2012-03-07 22:56 ` Olof Johansson

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=20210109064602.GU6918@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=torvalds@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

Powered by JetHome