All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Xin Ji <xji@analogixsemi.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kbuild-all@lists.01.org, bliang@analogixsemi.com,
	qwen@analogixsemi.com, jli@analogixsemi.com,
	Xin Ji <xji@analogixsemi.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 2/2] usb: typec: anx7411: Add Analogix PD ANX7411 support
Date: Mon, 24 Jan 2022 20:14:13 +0800	[thread overview]
Message-ID: <202201242014.N4URst2I-lkp@intel.com> (raw)
In-Reply-To: <20220121061856.2038958-2-xji@analogixsemi.com>

Hi Xin,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on usb/usb-testing]
[also build test WARNING on robh/for-next peter-chen-usb/for-usb-next v5.17-rc1 next-20220124]
[cannot apply to balbi-usb/testing/next]
[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]

url:    https://github.com/0day-ci/linux/commits/Xin-Ji/dt-bindings-usb-Add-analogix-anx7411-PD-binding/20220121-142000
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: s390-randconfig-s031-20220124 (https://download.01.org/0day-ci/archive/20220124/202201242014.N4URst2I-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/0day-ci/linux/commit/f75d15d4f011dabf8a702d85fb788f9aefb326e2
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Xin-Ji/dt-bindings-usb-Add-analogix-anx7411-PD-binding/20220121-142000
        git checkout f75d15d4f011dabf8a702d85fb788f9aefb326e2
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=s390 SHELL=/bin/bash drivers/irqchip/ drivers/usb/typec/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/usb/typec/anx7411.c:636:28: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] @@     got restricted __le32 [usertype] @@
   drivers/usb/typec/anx7411.c:636:28: sparse:     expected unsigned int [usertype]
   drivers/usb/typec/anx7411.c:636:28: sparse:     got restricted __le32 [usertype]

vim +636 drivers/usb/typec/anx7411.c

   621	
   622	static void anx7411_translate_payload(struct device *dev, u32 *payload,
   623					      u32 *pdo, int nr, const char *type)
   624	{
   625		int i;
   626	
   627		dev_info(dev, "convert %s pdos to little endian format\n", type);
   628		if (nr > PDO_MAX_OBJECTS) {
   629			dev_err(dev, "nr(%d) exceed PDO_MAX_OBJECTS(%d)\n",
   630				nr, PDO_MAX_OBJECTS);
   631	
   632			return;
   633		}
   634	
   635		for (i = 0; i < nr; i++)
 > 636			payload[i] = cpu_to_le32(pdo[i]);
   637	}
   638	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 2/2] usb: typec: anx7411: Add Analogix PD ANX7411 support
Date: Mon, 24 Jan 2022 20:14:13 +0800	[thread overview]
Message-ID: <202201242014.N4URst2I-lkp@intel.com> (raw)
In-Reply-To: <20220121061856.2038958-2-xji@analogixsemi.com>

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

Hi Xin,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on usb/usb-testing]
[also build test WARNING on robh/for-next peter-chen-usb/for-usb-next v5.17-rc1 next-20220124]
[cannot apply to balbi-usb/testing/next]
[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]

url:    https://github.com/0day-ci/linux/commits/Xin-Ji/dt-bindings-usb-Add-analogix-anx7411-PD-binding/20220121-142000
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: s390-randconfig-s031-20220124 (https://download.01.org/0day-ci/archive/20220124/202201242014.N4URst2I-lkp(a)intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/0day-ci/linux/commit/f75d15d4f011dabf8a702d85fb788f9aefb326e2
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Xin-Ji/dt-bindings-usb-Add-analogix-anx7411-PD-binding/20220121-142000
        git checkout f75d15d4f011dabf8a702d85fb788f9aefb326e2
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=s390 SHELL=/bin/bash drivers/irqchip/ drivers/usb/typec/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/usb/typec/anx7411.c:636:28: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] @@     got restricted __le32 [usertype] @@
   drivers/usb/typec/anx7411.c:636:28: sparse:     expected unsigned int [usertype]
   drivers/usb/typec/anx7411.c:636:28: sparse:     got restricted __le32 [usertype]

vim +636 drivers/usb/typec/anx7411.c

   621	
   622	static void anx7411_translate_payload(struct device *dev, u32 *payload,
   623					      u32 *pdo, int nr, const char *type)
   624	{
   625		int i;
   626	
   627		dev_info(dev, "convert %s pdos to little endian format\n", type);
   628		if (nr > PDO_MAX_OBJECTS) {
   629			dev_err(dev, "nr(%d) exceed PDO_MAX_OBJECTS(%d)\n",
   630				nr, PDO_MAX_OBJECTS);
   631	
   632			return;
   633		}
   634	
   635		for (i = 0; i < nr; i++)
 > 636			payload[i] = cpu_to_le32(pdo[i]);
   637	}
   638	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2022-01-24 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21  6:18 [PATCH v3 1/2] dt-bindings: usb: Add analogix anx7411 PD binding Xin Ji
2022-01-21  6:18 ` [PATCH v3 2/2] usb: typec: anx7411: Add Analogix PD ANX7411 support Xin Ji
2022-01-24 12:14   ` kernel test robot [this message]
2022-01-24 12:14     ` kernel test robot
2022-02-05  2:27 ` [PATCH v3 1/2] dt-bindings: usb: Add analogix anx7411 PD binding Rob Herring

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=202201242014.N4URst2I-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bliang@analogixsemi.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jli@analogixsemi.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=qwen@analogixsemi.com \
    --cc=xji@analogixsemi.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.