linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: shiju.jose@huawei.com, linux-cxl@vger.kernel.org,
	linux-mm@kvack.org, dave@stgolabs.net,
	jonathan.cameron@huawei.com, dave.jiang@intel.com,
	alison.schofield@intel.com, vishal.l.verma@intel.com,
	ira.weiny@intel.com, dan.j.williams@intel.com
Cc: oe-kbuild-all@lists.linux.dev, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, david@redhat.com,
	Vilas.Sridharan@amd.com, leo.duran@amd.com,
	Yazen.Ghannam@amd.com, rientjes@google.com, jiaqiyan@google.com,
	tony.luck@intel.com, Jon.Grimm@amd.com,
	dave.hansen@linux.intel.com, rafael@kernel.org, lenb@kernel.org,
	naoya.horiguchi@nec.com, james.morse@arm.com,
	jthoughton@google.com, somasundaram.a@hpe.com,
	erdemaktas@google.com, pgonda@google.com, duenwen@google.com,
	mike.malvestuto@intel.com
Subject: Re: [PATCH v3 02/11] cxl/mbox: Add GET_FEATURE mailbox command
Date: Fri, 24 Nov 2023 23:23:34 +0800	[thread overview]
Message-ID: <202311241607.cZbPFKOR-lkp@intel.com> (raw)
In-Reply-To: <20231123174355.1176-3-shiju.jose@huawei.com>

Hi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on krzk-mem-ctrl/for-next]
[also build test WARNING on linus/master v6.7-rc2 next-20231124]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/shiju-jose-huawei-com/cxl-mbox-Add-GET_SUPPORTED_FEATURES-mailbox-command/20231124-014622
base:   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git for-next
patch link:    https://lore.kernel.org/r/20231123174355.1176-3-shiju.jose%40huawei.com
patch subject: [PATCH v3 02/11] cxl/mbox: Add GET_FEATURE mailbox command
config: i386-randconfig-061-20231124 (https://download.01.org/0day-ci/archive/20231124/202311241607.cZbPFKOR-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231124/202311241607.cZbPFKOR-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311241607.cZbPFKOR-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   drivers/cxl/core/mbox.c:1317:30: sparse: sparse: cast from restricted __le32
>> drivers/cxl/core/mbox.c:1339:30: sparse: sparse: cast from restricted __le16
   drivers/cxl/core/mbox.c:1341:29: sparse: sparse: cast from restricted __le16

vim +1339 drivers/cxl/core/mbox.c

  1328	
  1329	int cxl_get_feature(struct cxl_memdev_state *mds,
  1330			    struct cxl_mbox_get_feat_in *pi, void *feat_out)
  1331	{
  1332		struct cxl_mbox_cmd mbox_cmd;
  1333		int rc;
  1334	
  1335		mbox_cmd = (struct cxl_mbox_cmd) {
  1336			.opcode = CXL_MBOX_OP_GET_FEATURE,
  1337			.size_in = sizeof(*pi),
  1338			.payload_in = pi,
> 1339			.size_out = (size_t)pi->count,
  1340			.payload_out = feat_out,
  1341			.min_out = (size_t)pi->count,
  1342		};
  1343		rc = cxl_internal_send_cmd(mds, &mbox_cmd);
  1344		if (rc < 0)
  1345			return rc;
  1346	
  1347		return 0;
  1348	}
  1349	EXPORT_SYMBOL_NS_GPL(cxl_get_feature, CXL);
  1350	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  reply	other threads:[~2023-11-24 15:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 17:43 [PATCH v3 00/11] cxl: Add support for CXL feature commands, CXL device patrol scrub control and DDR5 ECS control features shiju.jose
2023-11-23 17:43 ` [PATCH v3 01/11] cxl/mbox: Add GET_SUPPORTED_FEATURES mailbox command shiju.jose
2023-11-24 13:20   ` kernel test robot
2023-11-24 16:05     ` Shiju Jose
2023-11-23 17:43 ` [PATCH v3 02/11] cxl/mbox: Add GET_FEATURE " shiju.jose
2023-11-24 15:23   ` kernel test robot [this message]
2023-11-23 17:43 ` [PATCH v3 03/11] cxl/mbox: Add SET_FEATURE " shiju.jose
2023-11-23 17:43 ` [PATCH v3 04/11] cxl/memscrub: Add CXL device patrol scrub control feature shiju.jose
2023-11-23 17:43 ` [PATCH v3 05/11] cxl/memscrub: Add CXL device DDR5 ECS " shiju.jose
2023-11-23 17:43 ` [PATCH v3 06/11] memory: scrub: Add scrub driver supports configuring memory scrubs in the system shiju.jose
2023-11-23 17:43 ` [PATCH v3 07/11] cxl/memscrub: Register CXL device patrol scrub with scrub configure driver shiju.jose
2023-11-23 17:43 ` [PATCH v3 08/11] memory: scrub: Add scrub control attributes for the DDR5 ECS shiju.jose
2023-11-23 17:43 ` [PATCH v3 09/11] cxl/memscrub: Register CXL device DDR5 ECS with scrub configure driver shiju.jose
2023-11-23 17:43 ` [PATCH v3 10/11] memory: scrub: sysfs: Add Documentation for set of common scrub attributes shiju.jose
2023-11-23 17:43 ` [PATCH v3 11/11] cxl: scrub: sysfs: Add Documentation for CXL memory device scrub control attributes shiju.jose
2023-11-24 14:39   ` kernel test robot

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=202311241607.cZbPFKOR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jon.Grimm@amd.com \
    --cc=Vilas.Sridharan@amd.com \
    --cc=Yazen.Ghannam@amd.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=david@redhat.com \
    --cc=duenwen@google.com \
    --cc=erdemaktas@google.com \
    --cc=ira.weiny@intel.com \
    --cc=james.morse@arm.com \
    --cc=jiaqiyan@google.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=jthoughton@google.com \
    --cc=lenb@kernel.org \
    --cc=leo.duran@amd.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.malvestuto@intel.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pgonda@google.com \
    --cc=rafael@kernel.org \
    --cc=rientjes@google.com \
    --cc=shiju.jose@huawei.com \
    --cc=somasundaram.a@hpe.com \
    --cc=tony.luck@intel.com \
    --cc=vishal.l.verma@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).