From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "alexander.h.duyck@linux.intel.com" <alexander.h.duyck@linux.intel.com>
Cc: "zwisler@kernel.org" <zwisler@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH 2/2] nvdimm: Set device node in nd_device_register
Date: Tue, 25 Sep 2018 21:50:29 +0000 [thread overview]
Message-ID: <1537912228.7585.93.camel@intel.com> (raw)
In-Reply-To: <c6a5b7b0-954a-d84f-4927-03e51a016394@linux.intel.com>
On Tue, 2018-09-25 at 14:35 -0700, Alexander Duyck wrote:
[..]
> Yeah, I kind of gathered that. If you want to move it feel free to.
Thanks for the flexibility, applied.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "alexander.h.duyck@linux.intel.com" <alexander.h.duyck@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"Jiang, Dave" <dave.jiang@intel.com>,
"zwisler@kernel.org" <zwisler@kernel.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>
Subject: Re: [PATCH 2/2] nvdimm: Set device node in nd_device_register
Date: Tue, 25 Sep 2018 21:50:29 +0000 [thread overview]
Message-ID: <1537912228.7585.93.camel@intel.com> (raw)
In-Reply-To: <c6a5b7b0-954a-d84f-4927-03e51a016394@linux.intel.com>
On Tue, 2018-09-25 at 14:35 -0700, Alexander Duyck wrote:
[..]
> Yeah, I kind of gathered that. If you want to move it feel free to.
Thanks for the flexibility, applied.
next prev parent reply other threads:[~2018-09-25 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 20:52 [PATCH 0/2] Minor fixups for nd_device_register Alexander Duyck
2018-09-25 20:52 ` Alexander Duyck
2018-09-25 20:53 ` [PATCH 1/2] nvdimm: Hold reference on parent while scheduling async init Alexander Duyck
2018-09-25 20:53 ` Alexander Duyck
2018-09-25 21:09 ` Dan Williams
2018-09-25 21:09 ` Dan Williams
2018-09-25 20:53 ` [PATCH 2/2] nvdimm: Set device node in nd_device_register Alexander Duyck
2018-09-25 20:53 ` Alexander Duyck
2018-09-25 21:08 ` Dan Williams
2018-09-25 21:08 ` Dan Williams
2018-09-25 21:11 ` Alexander Duyck
2018-09-25 21:11 ` Alexander Duyck
2018-09-25 21:32 ` Dan Williams
2018-09-25 21:32 ` Dan Williams
2018-09-25 21:35 ` Alexander Duyck
2018-09-25 21:35 ` Alexander Duyck
2018-09-25 21:50 ` Williams, Dan J [this message]
2018-09-25 21:50 ` Williams, Dan J
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=1537912228.7585.93.camel@intel.com \
--to=dan.j.williams@intel.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=zwisler@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.