From: Johannes Thumshirn <jthumshirn@suse.de>
To: Linda Knippers <linda.knippers@hpe.com>
Cc: linux-nvdimm@lists.01.org
Subject: Re: [PATCH v3 0/3] apci, nfit: DSM improvements
Date: Fri, 31 Mar 2017 15:31:23 +0200 [thread overview]
Message-ID: <20170331133123.GC3848@linux-x5ow.site> (raw)
In-Reply-To: <58DE5755.1090900@hpe.com>
On Fri, Mar 31, 2017 at 09:19:17AM -0400, Linda Knippers wrote:
> On 03/31/2017 05:01 AM, Johannes Thumshirn wrote:
> > On Tue, Mar 07, 2017 at 04:35:11PM -0500, Linda Knippers wrote:
> >> The first two patches in this series are motivated by feedback
> >> from distribution developers, test engineers, and management tool
> >> developers. We need the ability to test and support Linux and
> >> management tools on systems that support more than one DSM family
> >> for NVDIMM-N.
> >>
> >> We also need the ability to test and support new functions without
> >> requiring users to update their kernel. These changes will also
> >> facilate development as we move toward DSM standardization.
> >> The ability to restrict DSM functions to the currently documented
> >> set is still in place.
> >>
> >> The third patch cleans up a cosmetic/modinfo parsing issue with one
> >> of the existing module parameters.
> >
> > Hi Linda and Dan,
> >
> > Can you tell me the status of this series? I haven't seen it in Dan's
> > tree and can't remember a reason why it's not merged.
>
> I assume/hope it's just waiting for the next merge window.
> At this point I think Dan is just pulling in critical fixes.
> If there's some other reason, I'd like to hear about it too.
OK.
Dan is it possible to do a for-next branch or a for-4.12 branch?
That'll make my life a _much_ easier.
Thanks,
Johanens
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-03-31 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 21:35 [PATCH v3 0/3] apci, nfit: DSM improvements Linda Knippers
2017-03-07 21:35 ` [PATCH 1/3] Allow override of built-in bitmasks for NVDIMM DSMs Linda Knippers
2017-03-07 21:35 ` [PATCH 2/3] Allow specifying a default DSM family Linda Knippers
2017-03-07 21:35 ` [PATCH 3/3] Remove unnecessary newline Linda Knippers
2017-03-31 9:01 ` [PATCH v3 0/3] apci, nfit: DSM improvements Johannes Thumshirn
2017-03-31 13:19 ` Linda Knippers
2017-03-31 13:31 ` Johannes Thumshirn [this message]
2017-03-31 13:54 ` Dan Williams
2017-03-31 13:58 ` Johannes Thumshirn
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=20170331133123.GC3848@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=linda.knippers@hpe.com \
--cc=linux-nvdimm@lists.01.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