From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC 3/3] net: vertexcom: Add MSE102x SPI support
Date: Thu, 16 Sep 2021 12:57:51 +0800 [thread overview]
Message-ID: <202109161203.MiqEYCbY-lkp@intel.com> (raw)
In-Reply-To: <20210914151717.12232-4-stefan.wahren@i2se.com>
[-- Attachment #1: Type: text/plain, Size: 2541 bytes --]
Hi Stefan,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v5.15-rc1 next-20210915]
[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/Stefan-Wahren/add-Vertexcom-MSE102x-support/20210914-232404
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/09f1b772a438e7953db653d74e869c6981dd8d45
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Stefan-Wahren/add-Vertexcom-MSE102x-support/20210914-232404
git checkout 09f1b772a438e7953db653d74e869c6981dd8d45
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/vertexcom/mse102x.c:119:6: error: no previous prototype for 'mse102x_init_device_debugfs' [-Werror=missing-prototypes]
119 | void mse102x_init_device_debugfs(struct mse102x_net_spi *mses)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/net/ethernet/vertexcom/mse102x.c:128:6: error: no previous prototype for 'mse102x_remove_device_debugfs' [-Werror=missing-prototypes]
128 | void mse102x_remove_device_debugfs(struct mse102x_net_spi *mses)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/mse102x_init_device_debugfs +119 drivers/net/ethernet/vertexcom/mse102x.c
118
> 119 void mse102x_init_device_debugfs(struct mse102x_net_spi *mses)
120 {
121 mses->device_root = debugfs_create_dir(dev_name(&mses->mse102x.ndev->dev),
122 NULL);
123
124 debugfs_create_file("info", S_IFREG | 0444, mses->device_root, mses,
125 &mse102x_info_fops);
126 }
127
> 128 void mse102x_remove_device_debugfs(struct mse102x_net_spi *mses)
129 {
130 debugfs_remove_recursive(mses->device_root);
131 }
132
---
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: 66522 bytes --]
prev parent reply other threads:[~2021-09-16 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 15:17 [PATCH RFC 0/3] add Vertexcom MSE102x support Stefan Wahren
2021-09-14 15:17 ` [PATCH RFC 1/3] dt-bindings: add vendor Vertexcom Stefan Wahren
2021-09-21 20:55 ` Rob Herring
2021-09-14 15:17 ` [PATCH RFC 2/3] dt-bindings: net: add Vertexcom MSE102x support Stefan Wahren
2021-09-21 21:09 ` Rob Herring
2021-09-14 15:17 ` [PATCH RFC 3/3] net: vertexcom: Add MSE102x SPI support Stefan Wahren
2021-09-15 2:55 ` Jakub Kicinski
2021-09-15 21:17 ` Andrew Lunn
2021-09-16 11:12 ` Stefan Wahren
2021-09-16 12:35 ` Andrew Lunn
2021-09-21 21:07 ` Rob Herring
2021-09-16 11:26 ` Michael Heimpold
2021-09-16 12:46 ` Andrew Lunn
2021-09-16 4:57 ` kernel test robot [this message]
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=202109161203.MiqEYCbY-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.