From: kernel test robot <lkp@intel.com>
To: Zhihao Cheng <chengzhihao1@huawei.com>,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
boris.brezillon@bootlin.com
Cc: kbuild-all@lists.01.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, chengzhihao1@huawei.com,
yukuai3@huawei.com
Subject: Re: [PATCH] mtd: ftl: Initialize rq.limits.discard_granularity
Date: Wed, 16 Jun 2021 21:22:25 +0800 [thread overview]
Message-ID: <202106162146.fhX3mqHx-lkp@intel.com> (raw)
In-Reply-To: <20210613112942.2329192-1-chengzhihao1@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]
Hi Zhihao,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mtd/mtd/next]
[also build test WARNING on mtd/mtd/fixes linux/master linus/master v5.13-rc6 next-20210615]
[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/Zhihao-Cheng/mtd-ftl-Initialize-rq-limits-discard_granularity/20210616-134538
base: https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next
config: arc-allyesconfig (attached as .config)
compiler: arceb-elf-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/64ffb6f0cfd38ca3d47e7bef4674c52a14fe024d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Zhihao-Cheng/mtd-ftl-Initialize-rq-limits-discard_granularity/20210616-134538
git checkout 64ffb6f0cfd38ca3d47e7bef4674c52a14fe024d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/mtd/ftl.c:107: warning: "SECTOR_SIZE" redefined
107 | #define SECTOR_SIZE 512
|
In file included from drivers/mtd/ftl.c:73:
include/linux/blkdev.h:967: note: this is the location of the previous definition
967 | #define SECTOR_SIZE (1 << SECTOR_SHIFT)
|
vim +/SECTOR_SIZE +107 drivers/mtd/ftl.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 105
^1da177e4c3f41 Linus Torvalds 2005-04-16 106 /* Sector size -- shouldn't need to change */
^1da177e4c3f41 Linus Torvalds 2005-04-16 @107 #define SECTOR_SIZE 512
^1da177e4c3f41 Linus Torvalds 2005-04-16 108
^1da177e4c3f41 Linus Torvalds 2005-04-16 109
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 68093 bytes --]
next prev parent reply other threads:[~2021-06-16 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 11:29 [PATCH] mtd: ftl: Initialize rq.limits.discard_granularity Zhihao Cheng
2021-06-16 13:22 ` kernel test robot [this message]
2021-06-16 19: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=202106162146.fhX3mqHx-lkp@intel.com \
--to=lkp@intel.com \
--cc=boris.brezillon@bootlin.com \
--cc=chengzhihao1@huawei.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yukuai3@huawei.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