From: kernel test robot <lkp@intel.com>
To: Jyan Chou <jyanchou@realtek.com>,
jh80.chung@samsung.com, adrian.hunter@intel.com,
ulf.hansson@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, jyanchou@realtek.com,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
james.tai@realtek.com
Subject: Re: [PATCH] CMDQ feature is introduced to eMMC standard in v5.1, which can be used to improve performance.
Date: Tue, 20 Jun 2023 19:04:42 +0800 [thread overview]
Message-ID: <202306201816.tTRpHo0c-lkp@intel.com> (raw)
In-Reply-To: <20230616063731.17591-1-jyanchou@realtek.com>
Hi Jyan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.4-rc7 next-20230620]
[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/Jyan-Chou/CMDQ-feature-is-introduced-to-eMMC-standard-in-v5-1-which-can-be-used-to-improve-performance/20230616-143849
base: linus/master
patch link: https://lore.kernel.org/r/20230616063731.17591-1-jyanchou%40realtek.com
patch subject: [PATCH] CMDQ feature is introduced to eMMC standard in v5.1, which can be used to improve performance.
config: mips-allyesconfig (https://download.01.org/0day-ci/archive/20230620/202306201816.tTRpHo0c-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230620/202306201816.tTRpHo0c-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/202306201816.tTRpHo0c-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/mmc/host/dw_mmc_cqe.c:39:
>> drivers/mmc/host/dw_mmc_cqe.h:321: warning: "END" redefined
321 | #define END(x) ((x & 1) << 1)
|
In file included from arch/mips/include/asm/bitops.h:19,
from include/linux/bitops.h:68,
from drivers/mmc/host/dw_mmc_cqe.c:9:
arch/mips/include/asm/asm.h:69: note: this is the location of the previous definition
69 | #define END(function) \
|
drivers/mmc/host/dw_mmc_cqe.c:232:10: error: 'const struct cqhci_host_ops' has no member named 'setup_tran_desc'
232 | .setup_tran_desc = dw_mci_cqe_setup_tran_desc,
| ^~~~~~~~~~~~~~~
drivers/mmc/host/dw_mmc_cqe.c:232:28: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
232 | .setup_tran_desc = dw_mci_cqe_setup_tran_desc,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/mmc/host/dw_mmc_cqe.c:232:28: note: (near initialization for 'dw_mci_cqhci_host_ops')
drivers/mmc/host/dw_mmc_cqe.c:232:28: error: initialization of 'void (*)(struct mmc_host *)' from incompatible pointer type 'void (*)(struct mmc_data *, struct cqhci_host *, u8 *, int)' {aka 'void (*)(struct mmc_data *, struct cqhci_host *, unsigned char *, int)'} [-Werror=incompatible-pointer-types]
drivers/mmc/host/dw_mmc_cqe.c:232:28: note: (near initialization for 'dw_mci_cqhci_host_ops.pre_enable')
drivers/mmc/host/dw_mmc_cqe.c: In function 'dw_mci_cqe_read_rsp':
>> drivers/mmc/host/dw_mmc_cqe.c:283:37: warning: variable 'rsp_tmp' set but not used [-Wunused-but-set-variable]
283 | u32 rsp_tmp[4];
| ^~~~~~~
drivers/mmc/host/dw_mmc_cqe.c: In function 'dw_mci_cqe_err_handle':
>> drivers/mmc/host/dw_mmc_cqe.c:766:41: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
766 | if (err == -DW_MCI_NOT_READY)
| ^~
drivers/mmc/host/dw_mmc_cqe.c:769:49: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if'
769 | break;
| ^~~~~
In file included from include/linux/debugfs.h:16,
from drivers/mmc/host/dw_mmc_cqe.c:12:
drivers/mmc/host/dw_mmc_cqe.c: At top level:
drivers/mmc/host/dw_mmc_cqe.c:97:23: warning: 'dw_mci_cqe_req_fops' defined but not used [-Wunused-const-variable=]
97 | DEFINE_SHOW_ATTRIBUTE(dw_mci_cqe_req);
| ^~~~~~~~~~~~~~
include/linux/seq_file.h:202:37: note: in definition of macro 'DEFINE_SHOW_ATTRIBUTE'
202 | static const struct file_operations __name ## _fops = { \
| ^~~~~~
cc1: some warnings being treated as errors
vim +/END +321 drivers/mmc/host/dw_mmc_cqe.h
319
320 #define VALID(x) ((x & 1) << 0)
> 321 #define END(x) ((x & 1) << 1)
322 #define INT(x) ((x & 1) << 2)
323 #define ACT(x) ((x & 0x7) << 3)
324 #define DAT_LENGTH(x) ((x & 0xFFFF) << 16)
325
326
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-20 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 6:37 [PATCH] CMDQ feature is introduced to eMMC standard in v5.1, which can be used to improve performance Jyan Chou
2023-06-20 6:45 ` Adrian Hunter
2023-06-20 8:04 ` Jyan Chou [周芷安]
2023-06-20 8:09 ` Jyan Chou [周芷安]
2023-06-29 13:31 ` Adrian Hunter
2023-06-20 11:04 ` kernel test robot [this message]
2023-06-20 13:19 ` 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=202306201816.tTRpHo0c-lkp@intel.com \
--to=lkp@intel.com \
--cc=adrian.hunter@intel.com \
--cc=james.tai@realtek.com \
--cc=jh80.chung@samsung.com \
--cc=jyanchou@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ulf.hansson@linaro.org \
/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