linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@01.org, linux-nvdimm@ml01.01.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tools/testing/nvdimm: test get_config_size DSM failures
Date: Wed, 14 Sep 2016 11:41:53 +0800	[thread overview]
Message-ID: <201609141142.bs4dcrJ1%fengguang.wu@intel.com> (raw)
In-Reply-To: <147381653820.13555.4462846098098492278.stgit@dwillia2-desk3.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]

Hi Dan,

[auto build test WARNING on next-20160913]
[cannot apply to pm/linux-next linus/master linux/master v4.8-rc6 v4.8-rc5 v4.8-rc4 v4.8-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Dan-Williams/nfit-fail-DSMs-that-return-non-zero-status-by-default/20160914-093545
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   tools/testing/nvdimm//test/nfit.c: In function 'handle_show':
>> tools/testing/nvdimm//test/nfit.c:609:26: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'u32 {aka unsigned int}' [-Wformat=]
     return sprintf(buf, "%#lx", handle[dimm]);
                             ^

vim +609 tools/testing/nvdimm//test/nfit.c

   593	
   594		if (sscanf(dev_name(dev), "test_dimm%d", &dimm) != 1
   595				|| dimm >= NUM_DCR || dimm < 0)
   596			return -ENXIO;
   597		return dimm;
   598	}
   599	
   600	
   601	static ssize_t handle_show(struct device *dev, struct device_attribute *attr,
   602			char *buf)
   603	{
   604		int dimm = dimm_name_to_id(dev);
   605	
   606		if (dimm < 0)
   607			return dimm;
   608	
 > 609		return sprintf(buf, "%#lx", handle[dimm]);
   610	}
   611	DEVICE_ATTR_RO(handle);
   612	
   613	static ssize_t fail_cmd_show(struct device *dev, struct device_attribute *attr,
   614			char *buf)
   615	{
   616		int dimm = dimm_name_to_id(dev);
   617	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 37774 bytes --]

      reply	other threads:[~2016-09-14  3:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  1:28 [PATCH 0/2] nfit: fail DSMs that return an unknown status value Dan Williams
2016-09-14  1:28 ` [PATCH 1/2] nfit: fail DSMs that return non-zero status by default Dan Williams
2016-09-14  1:28 ` [PATCH 2/2] tools/testing/nvdimm: test get_config_size DSM failures Dan Williams
2016-09-14  3:41   ` kbuild test robot [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=201609141142.bs4dcrJ1%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.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;
as well as URLs for NNTP newsgroup(s).