All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vishal Verma <vishal.l.verma@intel.com>
To: linux-nvdimm@lists.01.org
Cc: linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Tony Luck <tony.luck@intel.com>
Subject: [PATCH 1/3] pmem: clarify a debug print in pmem_clear_poison
Date: Mon, 18 Jul 2016 18:44:58 -0600	[thread overview]
Message-ID: <1468889100-30698-2-git-send-email-vishal.l.verma@intel.com> (raw)
In-Reply-To: <1468889100-30698-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..29ab25b 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: 0x%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

_______________________________________________
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: Vishal Verma <vishal.l.verma@intel.com>
To: linux-nvdimm@lists.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-acpi@vger.kernel.org,
	Vishal Verma <vishal.l.verma@intel.com>
Subject: [PATCH 1/3] pmem: clarify a debug print in pmem_clear_poison
Date: Mon, 18 Jul 2016 18:44:58 -0600	[thread overview]
Message-ID: <1468889100-30698-2-git-send-email-vishal.l.verma@intel.com> (raw)
In-Reply-To: <1468889100-30698-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..29ab25b 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: 0x%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


  reply	other threads:[~2016-07-19  0:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  0:44 [PATCH 0/3] ARS rescanning triggered by latent errors or userspace Vishal Verma
2016-07-19  0:44 ` Vishal Verma
2016-07-19  0:44 ` Vishal Verma [this message]
2016-07-19  0:44   ` [PATCH 1/3] pmem: clarify a debug print in pmem_clear_poison Vishal Verma
2016-07-19 15:53   ` Dan Williams
2016-07-19 15:53     ` Dan Williams
2016-07-19 17:15     ` Verma, Vishal L
2016-07-19 17:15       ` Verma, Vishal L
2016-07-19 17:56       ` Vishal Verma
2016-07-19 17:56         ` Vishal Verma
2016-07-19  0:44 ` [PATCH 2/3] nfit, libnvdimm: allow an ARS rescan to be triggered on demand Vishal Verma
2016-07-19  0:44   ` Vishal Verma
2016-07-19 16:15   ` Dan Williams
2016-07-19 16:15     ` Dan Williams
2016-07-19 17:45     ` Vishal Verma
2016-07-19 17:45       ` Vishal Verma
2016-07-19 18:00       ` Dan Williams
2016-07-19 18:00         ` Dan Williams
2016-07-19 18:32         ` Vishal Verma
2016-07-19 18:32           ` Vishal Verma
2016-07-19  0:45 ` [PATCH 3/3] nfit: do an ARS rescan on hitting a latent media error Vishal Verma
2016-07-19  0:45   ` Vishal Verma
2016-07-19 16:24   ` Dan Williams
2016-07-19 16:24     ` Dan Williams
2016-07-19 17:55     ` Vishal Verma
2016-07-19 17:55       ` Vishal Verma

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=1468889100-30698-2-git-send-email-vishal.l.verma@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-nvdimm@lists.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 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.