From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] mmc: core: Export device/vendor ids from Common CIS for SDIO cards
Date: Wed, 27 May 2020 16:16:41 +0800 [thread overview]
Message-ID: <202005271657.ynaB47aF%lkp@intel.com> (raw)
In-Reply-To: <20200526154334.21222-2-pali@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
Hi "Pali,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on ulf.hansson-mmc/next linux/master v5.7-rc7]
[cannot apply to next-20200526]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Pali-Roh-r/mmc-core-Do-not-export-MMC_NAME-and-MODALIAS-mmc-block-for-SDIO-cards/20200526-235837
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 9cb1fd0efd195590b828b9b865421ad345a4a145
config: i386-randconfig-s001-20200527 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-240-gf0fe1cd9-dirty
# save the attached .config to linux build tree
make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/mmc/core/sdio.c:44:20: sparse: sparse: symbol 'sdio_type' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 33467 bytes --]
next prev parent reply other threads:[~2020-05-27 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 15:43 [PATCH 1/2] mmc: core: Do not export MMC_NAME= and MODALIAS=mmc:block for SDIO cards Pali Rohár
2020-05-26 15:43 ` [PATCH 2/2] mmc: core: Export device/vendor ids from Common CIS " Pali Rohár
2020-05-27 7:39 ` Ulf Hansson
2020-05-27 8:00 ` Pali Rohár
2020-05-27 8:13 ` Ulf Hansson
2020-05-27 8:16 ` kbuild test robot [this message]
2020-05-27 8:16 ` [RFC PATCH] mmc: core: sdio_type can be static kbuild test robot
2020-05-27 11:08 ` [PATCH v2 1/2] mmc: core: Do not export MMC_NAME= and MODALIAS=mmc:block for SDIO cards Pali Rohár
2020-05-27 11:08 ` [PATCH v2 2/2] mmc: core: Export device/vendor ids from Common CIS " Pali Rohár
2020-05-28 10:14 ` Ulf Hansson
2020-05-28 10:14 ` [PATCH v2 1/2] mmc: core: Do not export MMC_NAME= and MODALIAS=mmc:block " Ulf Hansson
2020-05-27 7:34 ` [PATCH " Ulf Hansson
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=202005271657.ynaB47aF%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.