From: Vishal Verma <vishal.l.verma@intel.com>
To: <linux-nvdimm@ml01.01.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Tony Luck <tony.luck@intel.com>, <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org,
Vishal Verma <vishal.l.verma@intel.com>
Subject: [PATCH v2 1/3] pmem: clarify a debug print in pmem_clear_poison
Date: Wed, 20 Jul 2016 19:50:48 -0600 [thread overview]
Message-ID: <1469065850-32401-2-git-send-email-vishal.l.verma@intel.com> (raw)
In-Reply-To: <1469065850-32401-1-git-send-email-vishal.l.verma@intel.com>
Prefix the sector number being cleared with a '0x' to make it clear that
this is a hex value.
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
---
drivers/nvdimm/pmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
index 608fc44..08ac2cb 100644
--- a/drivers/nvdimm/pmem.c
+++ b/drivers/nvdimm/pmem.c
@@ -57,7 +57,7 @@ static void pmem_clear_poison(struct pmem_device *pmem, phys_addr_t offset,
cleared = nvdimm_clear_poison(dev, pmem->phys_addr + offset, len);
if (cleared > 0 && cleared / 512) {
- dev_dbg(dev, "%s: %llx clear %ld sector%s\n",
+ dev_dbg(dev, "%s: %#llx clear %ld sector%s\n",
__func__, (unsigned long long) sector,
cleared / 512, cleared / 512 > 1 ? "s" : "");
badblocks_clear(&pmem->bb, sector, cleared / 512);
--
2.7.4
next prev parent reply other threads:[~2016-07-21 1:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 1:50 [PATCH v2 0/3] ARS rescanning triggered by latent errors or userspace Vishal Verma
2016-07-21 1:50 ` Vishal Verma [this message]
2016-07-21 1:50 ` [PATCH v2 2/3] nfit, libnvdimm: allow an ARS scrub to be triggered on demand Vishal Verma
2016-07-21 15:56 ` Dan Williams
2016-07-21 18:07 ` Vishal Verma
2016-07-21 19:40 ` Linda Knippers
2016-07-21 19:46 ` Dan Williams
2016-07-21 19:55 ` Linda Knippers
2016-07-21 19:59 ` Dan Williams
2016-07-21 1:50 ` [PATCH v2 3/3] nfit: do an ARS scrub on hitting a latent media error Vishal Verma
2016-07-21 20:54 ` Linda Knippers
2016-07-21 21:10 ` Vishal Verma
2016-07-21 21:25 ` Linda Knippers
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=1469065850-32401-2-git-send-email-vishal.l.verma@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).