nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
	Ira Weiny <ira.weiny@intel.com>,
	 "Oliver O'Halloran" <oohall@gmail.com>,
	Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
	 Dave Jiang <dave.jiang@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	nvdimm@lists.linux.dev,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Move nvdimm mailing list
Date: Thu, 29 Apr 2021 14:49:00 -0700	[thread overview]
Message-ID: <CAPcyv4iDhrueShBUYMNAtUwMBmxtfrqOFjzoQ7KpN4aTTWrVpg@mail.gmail.com> (raw)
In-Reply-To: <87sg3bd8iv.fsf@meer.lwn.net>

On Tue, Apr 27, 2021 at 8:58 AM Jonathan Corbet <corbet@lwn.net> wrote:
>
> Dan Williams <dan.j.williams@intel.com> writes:
>
> > After seeing some users have subscription management trouble, more spam
> > than other Linux development lists, and considering some of the benefits
> > of kernel.org hosted lists, nvdimm and persistent memory development is
> > moving to nvdimm@lists.linux.dev.
> >
> > The old list will remain up until v5.14-rc1 and shutdown thereafter.
> >
> > Cc: Ira Weiny <ira.weiny@intel.com>
> > Cc: Oliver O'Halloran <oohall@gmail.com>
> > Cc: Matthew Wilcox <willy@infradead.org>
> > Cc: Jan Kara <jack@suse.cz>
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: Dave Jiang <dave.jiang@intel.com>
> > Cc: Vishal Verma <vishal.l.verma@intel.com>
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> > ---
> >  Documentation/ABI/obsolete/sysfs-class-dax    |    2 +
> >  Documentation/ABI/removed/sysfs-bus-nfit      |    2 +
> >  Documentation/ABI/testing/sysfs-bus-nfit      |   40 +++++++++++++------------
> >  Documentation/ABI/testing/sysfs-bus-papr-pmem |    4 +--
> >  Documentation/driver-api/nvdimm/nvdimm.rst    |    2 +
> >  MAINTAINERS                                   |   14 ++++-----
> >  6 files changed, 32 insertions(+), 32 deletions(-)
>
> Would you like me to take this through docs-next, or did you have
> another path in mind?

Thanks for the offer, I have a few other nvdimm related bits for this
cycle, so it can go through nvdimm.git.

  reply	other threads:[~2021-04-29 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  7:05 [PATCH] MAINTAINERS: Move nvdimm mailing list Dan Williams
2021-04-27 15:58 ` Jonathan Corbet
2021-04-29 21:49   ` Dan Williams [this message]
2021-05-14  0:58 ` Dan Williams

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=CAPcyv4iDhrueShBUYMNAtUwMBmxtfrqOFjzoQ7KpN4aTTWrVpg@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=corbet@lwn.net \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=oohall@gmail.com \
    --cc=vishal.l.verma@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).