From: kernel test robot <lkp@intel.com>
To: Jyan Chou <jyanchou@realtek.com>,
adrian.hunter@intel.com, ulf.hansson@linaro.org,
jh80.chung@samsung.com
Cc: oe-kbuild-all@lists.linux.dev, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, benchuanggli@gmail.com,
jyanchou@realtek.com
Subject: Re: [PATCH V2][1/4] mmc: solve DMA boundary limitation of CQHCI driver
Date: Thu, 19 Oct 2023 17:00:29 +0800 [thread overview]
Message-ID: <202310191631.Hp1KsdtD-lkp@intel.com> (raw)
In-Reply-To: <20231018055326.18256-2-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 ulf-hansson-mmc-mirror/next v6.6-rc6 next-20231018]
[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-solve-DMA-boundary-limitation-of-CQHCI-driver/20231018-135532
base: linus/master
patch link: https://lore.kernel.org/r/20231018055326.18256-2-jyanchou%40realtek.com
patch subject: [PATCH V2][1/4] mmc: solve DMA boundary limitation of CQHCI driver
config: csky-randconfig-001-20231019 (https://download.01.org/0day-ci/archive/20231019/202310191631.Hp1KsdtD-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231019/202310191631.Hp1KsdtD-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/202310191631.Hp1KsdtD-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/mmc/host/sdhci_am654.c:17:
>> drivers/mmc/host/cqhci.h:292:40: warning: 'struct mmc_data' declared inside parameter list will not be visible outside of this definition or declaration
292 | void (*setup_tran_desc)(struct mmc_data *data,
| ^~~~~~~~
--
>> drivers/mmc/host/cqhci-core.c:477:6: warning: no previous prototype for 'cqhci_set_tran_desc' [-Wmissing-prototypes]
477 | void cqhci_set_tran_desc(u8 *desc, dma_addr_t addr, int len, bool end,
| ^~~~~~~~~~~~~~~~~~~
vim +292 drivers/mmc/host/cqhci.h
281
282 struct cqhci_host_ops {
283 void (*dumpregs)(struct mmc_host *mmc);
284 void (*write_l)(struct cqhci_host *host, u32 val, int reg);
285 u32 (*read_l)(struct cqhci_host *host, int reg);
286 void (*enable)(struct mmc_host *mmc);
287 void (*disable)(struct mmc_host *mmc, bool recovery);
288 void (*update_dcmd_desc)(struct mmc_host *mmc, struct mmc_request *mrq,
289 u64 *data);
290 void (*pre_enable)(struct mmc_host *mmc);
291 void (*post_disable)(struct mmc_host *mmc);
> 292 void (*setup_tran_desc)(struct mmc_data *data,
293 struct cqhci_host *cq_host, u8 *desc, int sg_count);
294 #ifdef CONFIG_MMC_CRYPTO
295 int (*program_key)(struct cqhci_host *cq_host,
296 const union cqhci_crypto_cfg_entry *cfg, int slot);
297 #endif
298 };
299
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-19 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 5:53 [PATCH V2][0/4] Add DesignWare Mobile mmc driver Jyan Chou
2023-10-18 5:53 ` [PATCH V2][1/4] mmc: solve DMA boundary limitation of CQHCI driver Jyan Chou
2023-10-19 9:00 ` kernel test robot [this message]
2023-10-19 13:00 ` kernel test robot
2023-10-18 5:53 ` [PATCH V2][2/4] mmc: Add Synopsys DesignWare mmc cmdq host driver Jyan Chou
2023-10-18 5:53 ` [PATCH V2][3/4] mmc: Add dw mobile mmc cmdq rtk driver Jyan Chou
2023-10-18 5:53 ` [PATCH V2][4/4] mmc: Add dt-bindings for realtek mmc driver Jyan Chou
2023-10-18 14:24 ` Krzysztof Kozlowski
2023-10-20 5:18 ` Jyan Chou [周芷安]
2023-10-21 11:46 ` 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=202310191631.Hp1KsdtD-lkp@intel.com \
--to=lkp@intel.com \
--cc=adrian.hunter@intel.com \
--cc=benchuanggli@gmail.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