Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v3 0/3] apci, nfit: DSM improvements
Date: Fri, 31 Mar 2017 15:58:44 +0200	[thread overview]
Message-ID: <20170331135844.GD3848@linux-x5ow.site> (raw)
In-Reply-To: <CAPcyv4jAQoJwTc6a9KvYQc4TnD4ZDRdaf82DXPqtb=fDgMNBDQ@mail.gmail.com>

On Fri, Mar 31, 2017 at 06:54:13AM -0700, Dan Williams wrote:
> 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.

Thanks a lot.

       Joahnnes
-- 
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

      reply	other threads:[~2017-03-31 13:58 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
2017-03-31 13:54       ` Dan Williams
2017-03-31 13:58         ` Johannes Thumshirn [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=20170331135844.GD3848@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=dan.j.williams@intel.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