From: kernel test robot <lkp@intel.com>
To: wg@grandegger.com, mkl@pengutronix.de
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
andreas.geissler@duagon.com,
Abhijeet Badurkar <abhijeet.badurkar@duagon.com>
Subject: Re: [PATCH v2] Introduce MEN 16Z192-00 CAN controller driver
Date: Fri, 19 Jun 2020 20:18:26 +0800 [thread overview]
Message-ID: <202006192000.0FL76XAq%lkp@intel.com> (raw)
In-Reply-To: <20200619080954.6761-1-abhijeet.badurkar@duagon.com>
[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]
Hi Abhijeet,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.8-rc1 next-20200618]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Abhijeet-Badurkar/Introduce-MEN-16Z192-00-CAN-controller-driver/20200619-161212
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5e857ce6eae7ca21b2055cca4885545e29228fe2
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 487ca07fcc75d52755c9fe2ee05bcb3b6eeeec44)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/net/can/men_z192_can.c:704:6: warning: no previous prototype for function 'men_z192_set_can_state' [-Wmissing-prototypes]
void men_z192_set_can_state(struct net_device *ndev)
^
drivers/net/can/men_z192_can.c:704:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void men_z192_set_can_state(struct net_device *ndev)
^
static
1 warning generated.
vim +/men_z192_set_can_state +704 drivers/net/can/men_z192_can.c
703
> 704 void men_z192_set_can_state(struct net_device *ndev)
705 {
706 struct men_z192 *priv = netdev_priv(ndev);
707 struct men_z192_regs __iomem *regs = priv->regs;
708 enum can_state rx_state, tx_state;
709 u32 status;
710
711 status = readl(®s->rx_tx_sts);
712
713 rx_state = bus_state_map[MEN_Z192_GET_RSTATE(status)];
714 tx_state = bus_state_map[MEN_Z192_GET_TSTATE(status)];
715
716 can_change_state(ndev, NULL, tx_state, rx_state);
717 }
718
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 75309 bytes --]
prev parent reply other threads:[~2020-06-19 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 8:09 [PATCH v2] Introduce MEN 16Z192-00 CAN controller driver Abhijeet Badurkar
2020-06-19 10:47 ` kernel test robot
2020-06-19 12:18 ` 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=202006192000.0FL76XAq%lkp@intel.com \
--to=lkp@intel.com \
--cc=abhijeet.badurkar@duagon.com \
--cc=andreas.geissler@duagon.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).