From: kernel test robot <lkp@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Oded Gabbay <oded.gabbay@gmail.com>,
Omer Shpigelman <oshpigelman@habana.ai>,
Tomer Tayar <ttayar@habana.ai>,
Moti Haimovski <mhaimovski@habana.ai>,
Ofir Bitton <obitton@habana.ai>, Ben Segal <bpsegal20@gmail.com>,
Christine Gharzuzi <cgharzuzi@habana.ai>,
Pawel Piskorski <ppiskorski@habana.ai>
Subject: Re: [PATCH] habanalabs: fix up absolute include instructions
Date: Wed, 29 Jul 2020 07:27:07 +0800 [thread overview]
Message-ID: <202007290749.GIKjSISO%lkp@intel.com> (raw)
In-Reply-To: <20200728171851.55842-1-gregkh@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
Hi Greg,
I love your patch! Perhaps something to improve:
[auto build test WARNING on char-misc/char-misc-testing]
[cannot apply to linux/master linus/master v5.8-rc7 next-20200728]
[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/Greg-Kroah-Hartman/habanalabs-fix-up-absolute-include-instructions/20200729-012043
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git 65a9bde6ed484880987a6d88de6e372eca52059f
config: x86_64-randconfig-m001-20200728 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce (this is a W=1 build):
# 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 warnings (new ones prefixed by >>):
>> drivers/misc/habanalabs/goya/goya.c:5228:5: warning: no previous prototype for 'goya_ctx_init' [-Wmissing-prototypes]
5228 | int goya_ctx_init(struct hl_ctx *ctx)
| ^~~~~~~~~~~~~
--
>> drivers/misc/habanalabs/gaudi/gaudi.c:6275:5: warning: no previous prototype for 'gaudi_ctx_init' [-Wmissing-prototypes]
6275 | int gaudi_ctx_init(struct hl_ctx *ctx)
| ^~~~~~~~~~~~~~
vim +/goya_ctx_init +5228 drivers/misc/habanalabs/goya/goya.c
f8c8c7d5f1b0ea Oded Gabbay 2019-02-16 5227
a04b7cd97eef13 Ofir Bitton 2020-07-13 @5228 int goya_ctx_init(struct hl_ctx *ctx)
a04b7cd97eef13 Ofir Bitton 2020-07-13 5229 {
a04b7cd97eef13 Ofir Bitton 2020-07-13 5230 return 0;
a04b7cd97eef13 Ofir Bitton 2020-07-13 5231 }
a04b7cd97eef13 Ofir Bitton 2020-07-13 5232
---
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: 31595 bytes --]
next prev parent reply other threads:[~2020-07-28 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 17:18 [PATCH] habanalabs: fix up absolute include instructions Greg Kroah-Hartman
2020-07-28 22:09 ` Stephen Rothwell
2020-07-29 5:58 ` Greg Kroah-Hartman
2020-07-28 23:27 ` kernel test robot [this message]
2020-07-29 0:03 ` kernel test robot
2020-07-29 0:03 ` [RFC PATCH] habanalabs: goya_ctx_init() can be static 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=202007290749.GIKjSISO%lkp@intel.com \
--to=lkp@intel.com \
--cc=bpsegal20@gmail.com \
--cc=cgharzuzi@habana.ai \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhaimovski@habana.ai \
--cc=obitton@habana.ai \
--cc=oded.gabbay@gmail.com \
--cc=oshpigelman@habana.ai \
--cc=ppiskorski@habana.ai \
--cc=ttayar@habana.ai \
/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