From: Greg Ungerer <gerg@linux-m68k.org>
To: kernel test robot <lkp@intel.com>, Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: arch/m68k/68000/dragen2.c:73:16: error: 'screen_bits' undeclared
Date: Fri, 11 Jun 2021 00:44:38 +1000 [thread overview]
Message-ID: <b7d33ae8-24f5-cf5f-ba80-348b6c2e6853@linux-m68k.org> (raw)
In-Reply-To: <202106082234.K2ejj9O2-lkp@intel.com>
On 9/6/21 12:01 am, kernel test robot wrote:
> Hi Arnd,
>
> FYI, the error/warning still remains.
My fault. I have pushed the fix to the m68knommu git tree, for-next branch now.
See:
https://lore.kernel.org/linux-m68k/fd18edff-ddaf-e10c-5649-da0ade22dafa@linux-m68k.org/T/#t
Regards
Greg
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 614124bea77e452aa6df7a8714e8bc820b489922
> commit: a734bbf694270dca8594a5c33375867dc31503f5 m68k: m68328: move platform code to separate files
> date: 6 months ago
> config: m68k-randconfig-r021-20210608 (attached as .config)
> compiler: m68k-linux-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a734bbf694270dca8594a5c33375867dc31503f5
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout a734bbf694270dca8594a5c33375867dc31503f5
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
>
> 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 >>):
>
> arch/m68k/68000/dragen2.c:38:13: warning: no previous prototype for 'init_dragen2' [-Wmissing-prototypes]
> 38 | void __init init_dragen2(char *command, int size)
> | ^~~~~~~~~~~~
> arch/m68k/68000/dragen2.c: In function 'init_dragen2':
>>> arch/m68k/68000/dragen2.c:73:16: error: 'screen_bits' undeclared (first use in this function)
> 73 | LSSA = (long) screen_bits;
> | ^~~~~~~~~~~
> arch/m68k/68000/dragen2.c:73:16: note: each undeclared identifier is reported only once for each function it appears in
>
>
> vim +/screen_bits +73 arch/m68k/68000/dragen2.c
>
> 45
> 46 /* CSGB Init */
> 47 CSGBB = 0x4000;
> 48 CSB = 0x1a1;
> 49
> 50 /* CS8900 init */
> 51 /* PK3: hardware sleep function pin, active low */
> 52 PKSEL |= PK(3); /* select pin as I/O */
> 53 PKDIR |= PK(3); /* select pin as output */
> 54 PKDATA |= PK(3); /* set pin high */
> 55
> 56 /* PF5: hardware reset function pin, active high */
> 57 PFSEL |= PF(5); /* select pin as I/O */
> 58 PFDIR |= PF(5); /* select pin as output */
> 59 PFDATA &= ~PF(5); /* set pin low */
> 60
> 61 /* cs8900 hardware reset */
> 62 PFDATA |= PF(5);
> 63 { int i; for (i = 0; i < 32000; ++i); }
> 64 PFDATA &= ~PF(5);
> 65
> 66 /* INT1 enable (cs8900 IRQ) */
> 67 PDPOL &= ~PD(1); /* active high signal */
> 68 PDIQEG &= ~PD(1);
> 69 PDIRQEN |= PD(1); /* IRQ enabled */
> 70
> 71 #ifdef CONFIG_INIT_LCD
> 72 /* initialize LCD controller */
> > 73 LSSA = (long) screen_bits;
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
next prev parent reply other threads:[~2021-06-10 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 14:01 arch/m68k/68000/dragen2.c:73:16: error: 'screen_bits' undeclared kernel test robot
2021-06-10 14:44 ` Greg Ungerer [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-11 2:02 kernel test robot
2021-04-25 12:40 kernel test robot
2021-04-21 10:00 kernel test robot
2021-03-28 19:14 kernel test robot
2021-03-20 6:45 kernel test robot
2021-02-12 5:48 kernel test robot
2021-02-12 10:05 ` Arnd Bergmann
2021-02-11 13:46 kernel test robot
2020-12-29 2:18 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=b7d33ae8-24f5-cf5f-ba80-348b6c2e6853@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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).