From: kernel test robot <lkp@intel.com>
To: Jyan Chou <jyanchou@realtek.com>,
ulf.hansson@linaro.org, adrian.hunter@intel.com,
jh80.chung@samsung.com, riteshh@codeaurora.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, asutoshd@codeaurora.org,
p.zabel@pengutronix.de
Cc: oe-kbuild-all@lists.linux.dev, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
arnd@arndb.de, briannorris@chromium.org, doug@schmorgal.com,
tonyhuang.sunplus@gmail.com, abel.vesa@linaro.org,
william.qiu@starfivetech.com, jyanchou@realtek.com
Subject: Re: [PATCH V4][2/4] mmc: Add Synopsys DesignWare mmc cmdq host driver
Date: Wed, 1 Nov 2023 15:15:04 +0800 [thread overview]
Message-ID: <202311011551.QtHtdWmG-lkp@intel.com> (raw)
In-Reply-To: <20231030062749.2840-3-jyanchou@realtek.com>
Hi Jyan,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on ulf-hansson-mmc-mirror/next v6.6 next-20231031]
[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/mmc-Add-Synopsys-DesignWare-mmc-cmdq-host-driver/20231030-144300
base: linus/master
patch link: https://lore.kernel.org/r/20231030062749.2840-3-jyanchou%40realtek.com
patch subject: [PATCH V4][2/4] mmc: Add Synopsys DesignWare mmc cmdq host driver
config: sparc64-allyesconfig (https://download.01.org/0day-ci/archive/20231101/202311011551.QtHtdWmG-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231101/202311011551.QtHtdWmG-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/202311011551.QtHtdWmG-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/mmc/host/dw_mmc_cqe.c:227:10: error: 'const struct cqhci_host_ops' has no member named 'setup_tran_desc'
227 | .setup_tran_desc = dw_mci_cqe_setup_tran_desc,
| ^~~~~~~~~~~~~~~
>> drivers/mmc/host/dw_mmc_cqe.c:227:28: error: initialization of 'int (*)(struct cqhci_host *, const union cqhci_crypto_cfg_entry *, int)' 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]
227 | .setup_tran_desc = dw_mci_cqe_setup_tran_desc,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/mmc/host/dw_mmc_cqe.c:227:28: note: (near initialization for 'dw_mci_cqhci_host_ops.program_key')
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:96:23: warning: 'dw_mci_cqe_req_fops' defined but not used [-Wunused-const-variable=]
96 | 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 +227 drivers/mmc/host/dw_mmc_cqe.c
221
222 static const struct cqhci_host_ops dw_mci_cqhci_host_ops = {
223 .enable = dw_mci_cqe_enable,
224 .dumpregs = dw_mci_cqe_dumpregs,
225 .pre_enable = dw_mci_cqe_pre_enable,
226 .post_disable = dw_mci_cqe_post_disable,
> 227 .setup_tran_desc = dw_mci_cqe_setup_tran_desc,
228 };
229
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-01 7:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 6:27 [PATCH V4][0/4] Add DesignWare Mobile mmc driver Jyan Chou
2023-10-30 6:27 ` [PATCH V4][1/4] mmc: solve DMA boundary limitation of CQHCI driver Jyan Chou
2023-10-30 7:35 ` Krzysztof Kozlowski
2023-11-02 8:00 ` Jyan Chou [周芷安]
2023-10-30 6:27 ` [PATCH V4][2/4] mmc: Add Synopsys DesignWare mmc cmdq host driver Jyan Chou
2023-10-30 7:39 ` Krzysztof Kozlowski
2023-11-02 8:11 ` Jyan Chou [周芷安]
2023-11-01 7:15 ` kernel test robot [this message]
2023-10-30 6:27 ` [PATCH V4][3/4] mmc: Add dw mobile mmc cmdq rtk driver Jyan Chou
2023-10-30 7:44 ` Krzysztof Kozlowski
2023-10-31 3:47 ` Jyan Chou [周芷安]
2023-10-31 5:01 ` Krzysztof Kozlowski
2023-11-02 7:58 ` Jyan Chou [周芷安]
2023-10-30 6:27 ` [PATCH V4][4/4] dt-bindings: mmc: Add dt-bindings for realtek mmc driver Jyan Chou
2023-10-30 7:47 ` Krzysztof Kozlowski
2023-11-02 7:09 ` Jyan Chou [周芷安]
2023-11-02 7:14 ` Krzysztof Kozlowski
2023-11-02 7:38 ` Jyan Chou [周芷安]
2023-10-30 13:09 ` 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=202311011551.QtHtdWmG-lkp@intel.com \
--to=lkp@intel.com \
--cc=abel.vesa@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=asutoshd@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=doug@schmorgal.com \
--cc=jh80.chung@samsung.com \
--cc=jyanchou@realtek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=p.zabel@pengutronix.de \
--cc=riteshh@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=tonyhuang.sunplus@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=william.qiu@starfivetech.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