From: "Ira Weiny" <iweiny@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Alison Schofield" <alison.schofield@intel.com>
Cc: "Dan Williams" <djbw@kernel.org>,
"Vishal Verma" <vishal.l.verma@intel.com>,
"Dave Jiang" <dave.jiang@intel.com>,
nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] NVDIMM and DAX for 7.2
Date: Sun, 21 Jun 2026 21:07:54 -0500 [thread overview]
Message-ID: <0c692784-b09d-40cf-ad6b-abf067f72b20@app.fastmail.com> (raw)
In-Reply-To: <CAHk-=whPaVoqWyFEgTYW7LNZOegBmP3YFcrbxCmXTgqVjytdyA@mail.gmail.com>
On Thu, Jun 18, 2026, at 6:35 PM, Linus Torvalds wrote:
> On Thu, 18 Jun 2026 at 10:13, Alison Schofield
> <alison.schofield@intel.com> wrote:
>>
>> Please pull to receive a small set of NVDIMM and DAX changes. Also
>> included are updates to the MAINTAINER file, one which adds me as
>> I'm picking up the patch wrangling role from Ira Weiny.
>
> So I've pulled this, but generally I really prefer to have a heads-up
> ahead of time that I should expect to get pull requests from new
> maintainers.
>
> Yes, yes, I see the updates to maintainer files etc, but a "expect the
> next pull from Xyz" from the previous maintainer just makes me not
> have to wonder what's going on...
This is totally my fault as the last PR I did I was not ready to announce this change. I should have just sent an additional note about this.
Apologies,
Ira
>
> Linus
next prev parent reply other threads:[~2026-06-22 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 17:13 Alison Schofield
2026-06-18 23:35 ` Linus Torvalds
2026-06-22 2:07 ` Ira Weiny [this message]
2026-06-19 0:09 ` pr-tracker-bot
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=0c692784-b09d-40cf-ad6b-abf067f72b20@app.fastmail.com \
--to=iweiny@kernel.org \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=djbw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=vishal.l.verma@intel.com \
/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®