From: Dave Jiang <dave.jiang@intel.com>
To: Vinod Koul <vkoul@kernel.org>
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>,
Frank Li <Frank.Li@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update CXL, NVDIMM, DAX, and others for djbw
Date: Fri, 20 Nov 2026 08:47:58 -0700 [thread overview]
Message-ID: <0a0844b4-f0ce-47f2-b6f1-af45ad997155@intel.com> (raw)
In-Reply-To: <awAJxeXEA2yykiV-@parshuram>
On 11/20/26 1:50 AM, Vinod Koul wrote:
> Hi Dave,
>
> On 03-11-26, 13:15, Dave Jiang wrote:
>> Dan is no longer with us. Removing entries in MAINTAINERS to prevent
>> people from keep emailing his address.
>
> Can you please add the entry in Credits. We will miss Dan, his
> presence cannot go away, he stays always here.
I think Jason has already put those [1] in Credits and I've amended them for any missing entries. I definitely agree.
>
>
>>
>> async_tx will be essentially orphaned. There has been discussion of
>> deprecation for the feature on the dmaengine mailing list.
>
> I think we can fold this one into dmaengine entry as well
Guess I'm not understanding how you want this to look. I just replaced with Frank for now as he requested [2].
[1]: https://lore.kernel.org/all/0-v1-52697321555d+14e66-tsm_maintainer_jgg@nvidia.com/
[2]: https://lore.kernel.org/linux-cxl/d6a3c6a9-71f7-406d-9ae9-33b3566768eb@intel.com/T/#t
prev parent reply other threads:[~2026-11-20 15:48 UTC|newest]
Thread overview: 9+ 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
2026-11-04 15:54 ` Dave Jiang
2026-11-10 3:54 ` Jonathan Cameron
2026-11-20 8:50 ` Vinod Koul
2026-11-20 15:47 ` Dave Jiang [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=0a0844b4-f0ce-47f2-b6f1-af45ad997155@intel.com \
--to=dave.jiang@intel.com \
--cc=Frank.Li@kernel.org \
--cc=alison.schofield@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®