From: Fabian Frederick <fabf@skynet.be> To: Dan Williams <dan.j.williams@intel.com> Cc: fabf@skynet.be, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org Subject: [PATCH 3/8 linux-next] libnvdimm, namespace: move persistence warning Date: Fri, 2 Dec 2016 20:20:36 +0100 [thread overview] Message-ID: <1480706436-21058-1-git-send-email-fabf@skynet.be> (raw) There's no need to warn on persistence yet as some validity tests are on the way. Signed-off-by: Fabian Frederick <fabf@skynet.be> --- drivers/nvdimm/pmem.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c index 822a712..204912c 100644 --- a/drivers/nvdimm/pmem.c +++ b/drivers/nvdimm/pmem.c @@ -266,9 +266,6 @@ static int pmem_attach_disk(struct device *dev, dev_set_drvdata(dev, pmem); pmem->phys_addr = res->start; pmem->size = resource_size(res); - if (nvdimm_has_flush(nd_region) < 0) - dev_warn(dev, "unable to guarantee persistence of writes due to unknown flushing capability of the memory region\n"); - if (!devm_request_mem_region(dev, res->start, resource_size(res), dev_name(dev))) { dev_warn(dev, "could not reserve region %pR\n", res); @@ -279,6 +276,9 @@ static int pmem_attach_disk(struct device *dev, if (!q) return -ENOMEM; + if (nvdimm_has_flush(nd_region) < 0) + dev_warn(dev, "unable to guarantee persistence of writes due to unknown flushing capability of the memory region\n"); + pmem->pfn_flags = PFN_DEV; if (is_nd_pfn(dev)) { addr = devm_memremap_pages(dev, &pfn_res, &q->q_usage_counter, -- 2.7.4 _______________________________________________ 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: Fabian Frederick <fabf@skynet.be> To: Dan Williams <dan.j.williams@intel.com> Cc: linux-nvdimm@ml01.01.org, linux-kernel@vger.kernel.org, fabf@skynet.be Subject: [PATCH 3/8 linux-next] libnvdimm, namespace: move persistence warning Date: Fri, 2 Dec 2016 20:20:36 +0100 [thread overview] Message-ID: <1480706436-21058-1-git-send-email-fabf@skynet.be> (raw) There's no need to warn on persistence yet as some validity tests are on the way. Signed-off-by: Fabian Frederick <fabf@skynet.be> --- drivers/nvdimm/pmem.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c index 822a712..204912c 100644 --- a/drivers/nvdimm/pmem.c +++ b/drivers/nvdimm/pmem.c @@ -266,9 +266,6 @@ static int pmem_attach_disk(struct device *dev, dev_set_drvdata(dev, pmem); pmem->phys_addr = res->start; pmem->size = resource_size(res); - if (nvdimm_has_flush(nd_region) < 0) - dev_warn(dev, "unable to guarantee persistence of writes due to unknown flushing capability of the memory region\n"); - if (!devm_request_mem_region(dev, res->start, resource_size(res), dev_name(dev))) { dev_warn(dev, "could not reserve region %pR\n", res); @@ -279,6 +276,9 @@ static int pmem_attach_disk(struct device *dev, if (!q) return -ENOMEM; + if (nvdimm_has_flush(nd_region) < 0) + dev_warn(dev, "unable to guarantee persistence of writes due to unknown flushing capability of the memory region\n"); + pmem->pfn_flags = PFN_DEV; if (is_nd_pfn(dev)) { addr = devm_memremap_pages(dev, &pfn_res, &q->q_usage_counter, -- 2.7.4
next reply other threads:[~2016-12-02 19:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-02 19:20 Fabian Frederick [this message] 2016-12-02 19:20 ` [PATCH 3/8 linux-next] libnvdimm, namespace: move persistence warning Fabian Frederick 2016-12-02 20:51 ` Dan Williams 2016-12-02 20:51 ` 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=1480706436-21058-1-git-send-email-fabf@skynet.be \ --to=fabf@skynet.be \ --cc=dan.j.williams@intel.com \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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.