From: Frank Li <Frank.li@oss.nxp.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update CXL, NVDIMM, DAX, and others for djbw
Date: Wed, 4 Nov 2026 10:22:12 -0500 [thread overview]
Message-ID: <autNpAFXuBVywP8Q@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20261103201547.4079847-1-dave.jiang@intel.com>
On Tue, Nov 03, 2026 at 01:15:47PM -0700, Dave Jiang wrote:
> Dan is no longer with us. Removing entries in MAINTAINERS to prevent
> people from keep emailing his address.
>
> async_tx will be essentially orphaned. There has been discussion of
> deprecation for the feature on the dmaengine mailing list.
>
> fsdax will no longer have a maintainer. But there are reviewers still
> and Alison Schofield will continue to wrangle patches for DAX overall.
>
> Cc: Alison Schofield <alison.schofield@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Jan Kara <jack@suse.cz>
> Cc: Davidlohr Bueso <dave@stgolabs.net>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: Frank Li <Frank.Li@kernel.org>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
>
> ---
> For FSDAX, Jan or Willy if you guys want to step up and be the
> maintainer please let me know and I'll update the entry. Thanks.
> ---
> MAINTAINERS | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 14e4daf8ea8a..32b86033b5f1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4285,8 +4285,7 @@ S: Maintained
> F: crypto/rsa*
>
> ASYNCHRONOUS TRANSFERS/TRANSFORMS (IOAT) API
> -R: Dan Williams <djbw@kernel.org>
> -S: Odd fixes
> +S: Orphan
Can you put my name here now until it is full removed. I have some cleanup
patch need be merged in case take more time to remove it totally.
Frank
> W: http://sourceforge.net/projects/xscaleiop
> F: Documentation/crypto/async-tx-api.rst
> F: crypto/async_tx/
> @@ -6715,7 +6714,6 @@ M: Jonathan Cameron <jic23@kernel.org>
> M: Dave Jiang <dave.jiang@intel.com>
> M: Alison Schofield <alison.schofield@intel.com>
> M: Vishal Verma <vishal.l.verma@intel.com>
> -M: Dan Williams <djbw@kernel.org>
> R: Ira Weiny <iweiny@kernel.org>
> R: Li Ming <ming.li@zohomail.com>
> R: Richard Cheng <icheng@nvidia.com>
> @@ -7610,7 +7608,6 @@ S: Maintained
> F: scripts/dev-needs.sh
>
> DEVICE DIRECT ACCESS (DAX)
> -M: Dan Williams <djbw@kernel.org>
> M: Vishal Verma <vishal.l.verma@intel.com>
> M: Dave Jiang <dave.jiang@intel.com>
> M: Alison Schofield <alison.schofield@intel.com>
> @@ -10304,12 +10301,11 @@ F: include/linux/fcntl.h
> F: include/uapi/linux/fcntl.h
>
> FILESYSTEM DIRECT ACCESS (DAX)
> -M: Dan Williams <djbw@kernel.org>
> R: Matthew Wilcox <willy@infradead.org>
> R: Jan Kara <jack@suse.cz>
> L: linux-fsdevel@vger.kernel.org
> L: nvdimm@lists.linux.dev
> -S: Supported
> +S: Odd Fixes
> F: fs/dax.c
> F: include/linux/dax.h
> F: include/trace/events/fs_dax.h
> @@ -13444,7 +13440,6 @@ F: drivers/platform/x86/intel/hid.c
>
> INTEL I/OAT DMA DRIVER
> M: Dave Jiang <dave.jiang@intel.com>
> -R: Dan Williams <djbw@kernel.org>
> L: dmaengine@vger.kernel.org
> S: Supported
> Q: https://patchwork.kernel.org/project/linux-dmaengine/list/
> @@ -15267,7 +15262,6 @@ K: libie
>
> LIBNVDIMM BTT: BLOCK TRANSLATION TABLE
> M: Vishal Verma <vishal.l.verma@intel.com>
> -M: Dan Williams <djbw@kernel.org>
> M: Dave Jiang <dave.jiang@intel.com>
> M: Alison Schofield <alison.schofield@intel.com>
> L: nvdimm@lists.linux.dev
> @@ -15277,7 +15271,6 @@ P: Documentation/nvdimm/maintainer-entry-profile.rst
> F: drivers/nvdimm/btt*
>
> LIBNVDIMM PMEM: PERSISTENT MEMORY DRIVER
> -M: Dan Williams <djbw@kernel.org>
> M: Vishal Verma <vishal.l.verma@intel.com>
> M: Dave Jiang <dave.jiang@intel.com>
> M: Alison Schofield <alison.schofield@intel.com>
> @@ -15296,7 +15289,6 @@ F: Documentation/devicetree/bindings/pmem/pmem-region.yaml
> F: drivers/nvdimm/of_pmem.c
>
> LIBNVDIMM: NON-VOLATILE MEMORY DEVICE SUBSYSTEM
> -M: Dan Williams <djbw@kernel.org>
> M: Vishal Verma <vishal.l.verma@intel.com>
> M: Dave Jiang <dave.jiang@intel.com>
> M: Alison Schofield <alison.schofield@intel.com>
>
> base-commit: abf8c33470f78e2226ee3dcdc69004660020ab47
> --
> 2.54.0
>
next prev parent reply other threads:[~2026-11-04 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 20:15 Dave Jiang
2026-11-03 20:48 ` Davidlohr Bueso
2026-11-03 22:15 ` Verma, Vishal L
2026-11-04 3:06 ` Alison Schofield
2026-11-04 15:22 ` Frank Li [this message]
2026-11-04 15:54 ` Dave Jiang
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=autNpAFXuBVywP8Q@lizhi-Precision-Tower-5810 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=dmaengine@vger.kernel.org \
--cc=jack@suse.cz \
--cc=jic23@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.com \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®