linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Leonardo Brás" <leobras.c@gmail.com>
Cc: kbuild-all@01.org,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: fbtft: Moves ";" from macro definition to macro usage.
Date: Fri, 10 Aug 2018 19:27:54 +0800	[thread overview]
Message-ID: <201808101921.Ee4K5ZhN%fengguang.wu@intel.com> (raw)
In-Reply-To: <d3d79581fccabb25174f5679415c2f985d1271a4.1533857298.git.leobras.c@gmail.com>

Hi Leonardo,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.18-rc8 next-20180809]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Leonardo-Br-s/staging-fbtft-Moves-from-macro-definition-to-macro-usage/20180810-154004
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/staging/fbtft/fbtft-bus.c:66:1: sparse: incorrect type in assignment (different base types) @@    expected restricted __be16 [usertype] <noident> @@    got unsignedrestricted __be16 [usertype] <noident> @@
   drivers/staging/fbtft/fbtft-bus.c:66:1:    expected restricted __be16 [usertype] <noident>
   drivers/staging/fbtft/fbtft-bus.c:66:1:    got unsigned short [unsigned] [usertype] <noident>
>> drivers/staging/fbtft/fbtft-bus.c:66:1: sparse: incorrect type in assignment (different base types) @@    expected restricted __be16 [usertype] <noident> @@    got unsignedrestricted __be16 [usertype] <noident> @@
   drivers/staging/fbtft/fbtft-bus.c:66:1:    expected restricted __be16 [usertype] <noident>
   drivers/staging/fbtft/fbtft-bus.c:66:1:    got unsigned short [unsigned] [usertype] <noident>
>> drivers/staging/fbtft/fbtft-bus.c:66:1: sparse: incorrect type in assignment (different base types) @@    expected restricted __be16 [usertype] <noident> @@    got unsignedrestricted __be16 [usertype] <noident> @@
   drivers/staging/fbtft/fbtft-bus.c:66:1:    expected restricted __be16 [usertype] <noident>
   drivers/staging/fbtft/fbtft-bus.c:66:1:    got unsigned short [unsigned] [usertype] <noident>
   drivers/staging/fbtft/fbtft-bus.c:156:27: sparse: expression using sizeof(void)
   drivers/staging/fbtft/fbtft-bus.c:156:27: sparse: expression using sizeof(void)
   drivers/staging/fbtft/fbtft-bus.c:200:27: sparse: expression using sizeof(void)
   drivers/staging/fbtft/fbtft-bus.c:200:27: sparse: expression using sizeof(void)

vim +66 drivers/staging/fbtft/fbtft-bus.c

    64	
    65	define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8, );
  > 66	define_fbtft_write_reg(fbtft_write_reg16_bus8, __be16, u16, );
    67	define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16, );
    68	

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

  reply	other threads:[~2018-08-10 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1533857298.git.leobras.c@gmail.com>
2018-08-09 23:28 ` [PATCH 1/2] staging: fbtft: Moves ";" from macro definition to macro usage Leonardo Brás
2018-08-10 11:27   ` kbuild test robot [this message]
2018-08-09 23:29 ` [PATCH 2/2] staging: fbtft: Adds space around "/" Leonardo Brás

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=201808101921.Ee4K5ZhN%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=leobras.c@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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).