On Fri, Mar 31, 2017 at 6:31 AM, Johannes Thumshirn <[email protected]> wrote: > 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.
Yes, it's queued. I had been holding back updating my for-next branch while debugging some test regressions in other for-4.12 patches. However, I'll just kick those other patches out of the branch and post these. Thanks for the nudge. _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
