[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201907232128.QQzyQsOw%lkp@intel.com>
Date: Tue, 23 Jul 2019 21:43:52 +0800
From: kbuild test robot <lkp@...el.com>
To: Gabriel Beauchamp <beauchampgabriel@...il.com>
Cc: kbuild-all@...org, gregkh@...uxfoundation.org,
christian.gromm@...rochip.com, colin.king@...onical.com,
gustavo@...eddedor.com, joe@...ches.com,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
Gabriel Beauchamp <beauchampgabriel@...il.com>
Subject: Re: [PATCH v3] Staging: most: fix coding style issues
Hi Gabriel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
[cannot apply to v5.3-rc1 next-20190723]
[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/Gabriel-Beauchamp/Staging-most-fix-coding-style-issues/20190701-203804
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@...el.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/staging/most/core.c:308:30: sparse: sparse: incorrect type in assignment (different modifiers) @@ expected char *type @@ got char const *char *type @@
>> drivers/staging/most/core.c:308:30: sparse: expected char *type
>> drivers/staging/most/core.c:308:30: sparse: got char const *const name
vim +308 drivers/staging/most/core.c
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists