From: kernel test robot <lkp@intel.com>
To: Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, linux-fbdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Sven Schnelle <svens@stackframe.org>
Subject: Re: [PATCH v3] fbdev: visfxfb: HP Visualize-FX framebufffer driver
Date: Tue, 25 Apr 2023 18:58:43 +0800 [thread overview]
Message-ID: <202304251827.bmcNCFkF-lkp@intel.com> (raw)
In-Reply-To: <ZEWqkJekzyIlhBlW@p100>
Hi Helge,
kernel test robot noticed the following build warnings:
[auto build test WARNING on deller-parisc/for-next]
[also build test WARNING on linus/master v6.3 next-20230424]
[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/Helge-Deller/fbdev-visfxfb-HP-Visualize-FX-framebufffer-driver/20230424-060227
base: https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git for-next
patch link: https://lore.kernel.org/r/ZEWqkJekzyIlhBlW%40p100
patch subject: [PATCH v3] fbdev: visfxfb: HP Visualize-FX framebufffer driver
config: parisc-allyesconfig (https://download.01.org/0day-ci/archive/20230425/202304251827.bmcNCFkF-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 12.1.0
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
# https://github.com/intel-lab-lkp/linux/commit/96fac55bbf4fc2930b24f7a757369196a5d4940c
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Helge-Deller/fbdev-visfxfb-HP-Visualize-FX-framebufffer-driver/20230424-060227
git checkout 96fac55bbf4fc2930b24f7a757369196a5d4940c
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash drivers/video/fbdev/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304251827.bmcNCFkF-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/video/fbdev/visfxfb.c:1067:5: warning: no previous prototype for 'visfx_sync' [-Wmissing-prototypes]
1067 | int visfx_sync(struct fb_info *info)
| ^~~~~~~~~~
>> drivers/video/fbdev/visfxfb.c:1431:5: warning: no previous prototype for 'visfx_set_default_mode' [-Wmissing-prototypes]
1431 | int visfx_set_default_mode(struct fb_info *info)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/visfx_sync +1067 drivers/video/fbdev/visfxfb.c
1066
> 1067 int visfx_sync(struct fb_info *info)
1068 {
1069 visfx_wait_write_pipe_empty(info);
1070 return 0;
1071 }
1072
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-04-25 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 22:00 [PATCH v3] fbdev: visfxfb: HP Visualize-FX framebufffer driver Helge Deller
2023-04-25 10:58 ` 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=202304251827.bmcNCFkF-lkp@intel.com \
--to=lkp@intel.com \
--cc=deller@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=svens@stackframe.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;
as well as URLs for NNTP newsgroup(s).