linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	kernel test robot <lkp@intel.com>,
	 Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	oe-kbuild-all@lists.linux.dev,
	 Linux Memory Management List <linux-mm@kvack.org>,
	Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: [WARNING: ATTACHMENT UNSCANNED]Re: [linux-next:master 13230/13643] arch/riscv/errata/andes/errata.c:29:23: error: storage size of 'ret' isn't known
Date: Thu, 31 Aug 2023 12:22:50 +0100	[thread overview]
Message-ID: <CA+V-a8thx2qah2gJVG6mmrSCtnLTBRFS7fr+cpTMU-6RpqoaTQ@mail.gmail.com> (raw)
In-Reply-To: <20230831-congested-monument-44ddb496204d@wendy>

Hi Conor,

On Thu, Aug 31, 2023 at 10:44 AM Conor Dooley
<conor.dooley@microchip.com> wrote:
>
> On Thu, Aug 31, 2023 at 04:52:00PM +0800, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   a47fc304d2b678db1a5d760a7d644dac9b067752
> > commit: f2863f30d1b05e5ecf61c063609cb974954d47f8 [13230/13643] riscv: errata: Add Andes alternative ports
> > config: riscv-randconfig-001-20230831 (https://download.01.org/0day-ci/archive/20230831/202308311610.ec6bm2G8-lkp@intel.com/config)
> > compiler: riscv64-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230831/202308311610.ec6bm2G8-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202308311610.ec6bm2G8-lkp@intel.com/
> >
> > All error/warnings (new ones prefixed by >>):
> >
> >    arch/riscv/errata/andes/errata.c: In function 'ax45mp_iocp_sw_workaround':
> > >> arch/riscv/errata/andes/errata.c:29:23: error: storage size of 'ret' isn't known
> >       29 |         struct sbiret ret;
> >          |                       ^~~
> > >> arch/riscv/errata/andes/errata.c:35:15: error: implicit declaration of function 'sbi_ecall' [-Werror=implicit-function-declaration]
> >       35 |         ret = sbi_ecall(ANDESTECH_SBI_EXT_ANDES, ANDES_SBI_EXT_IOCP_SW_WORKAROUND,
> >          |               ^~~~~~~~~
> > >> arch/riscv/errata/andes/errata.c:29:23: warning: unused variable 'ret' [-Wunused-variable]
> >       29 |         struct sbiret ret;
> >          |                       ^~~
> >    cc1: some warnings being treated as errors
> >
> >
> > vim +29 arch/riscv/errata/andes/errata.c
> >
> >     26
> >     27        static long ax45mp_iocp_sw_workaround(void)
> >     28        {
> >   > 29                struct sbiret ret;
> >     30
> >     31                /*
> >     32                 * ANDES_SBI_EXT_IOCP_SW_WORKAROUND SBI EXT checks if the IOCP is missing and
> >     33                 * cache is controllable only then CMO will be applied to the platform.
> >     34                 */
> >   > 35                ret = sbi_ecall(ANDESTECH_SBI_EXT_ANDES, ANDES_SBI_EXT_IOCP_SW_WORKAROUND,
> >     36                                0, 0, 0, 0, 0, 0);
> >     37
> >     38                return ret.error ? 0 : ret.value;
> >     39        }
> >     40
>
> Looks like the config doesn't enable SBI, so ERRATA_ANDES_CMO will need
> to grow a dependency on RISCV_SBI.
I think adding dependency for RISCV_SBI on ERRATA_ANDES would be a good idea.

While at it I am seeing below warnings with this randconfig:
WARNING: unmet direct dependencies detected for ERRATA_ANDES_CMO
  Depends on [n]: ERRATA_ANDES [=y] && MMU [=n] && ARCH_R9A07G043 [=y]
  Selected by [y]:
  - ARCH_R9A07G043 [=y] && SOC_RENESAS [=y] && RISCV [=y]

WARNING: unmet direct dependencies detected for AX45MP_L2_CACHE
  Depends on [n]: RISCV_DMA_NONCOHERENT [=n]
  Selected by [y]:
  - ARCH_R9A07G043 [=y] && SOC_RENESAS [=y] && RISCV [=y]
configuration written to .config

*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.

For which I will send the below fix:
--- a/drivers/soc/renesas/Kconfig
+++ b/drivers/soc/renesas/Kconfig
@@ -334,10 +334,10 @@ if RISCV
 config ARCH_R9A07G043
     bool "RISC-V Platform support for RZ/Five"
     select ARCH_RZG2L
-    select AX45MP_L2_CACHE
+    imply AX45MP_L2_CACHE
     select DMA_GLOBAL_POOL
-    select ERRATA_ANDES
-    select ERRATA_ANDES_CMO
+    imply ERRATA_ANDES
+    imply ERRATA_ANDES_CMO
     help
       This enables support for the Renesas RZ/Five SoC.

Cheers,
Prabhakar


  reply	other threads:[~2023-08-31 11:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  8:52 kernel test robot
2023-08-31  9:16 ` [WARNING: ATTACHMENT UNSCANNED]Re: " Conor Dooley
2023-08-31 11:22   ` Lad, Prabhakar [this message]
2023-08-31 11:33     ` Conor Dooley
2023-08-31 11:53       ` Lad, Prabhakar
2023-08-31 12:01         ` Geert Uytterhoeven
2023-08-31 13:01           ` Lad, Prabhakar
2023-08-31 13:24             ` Geert Uytterhoeven
2023-08-31 14:59               ` Lad, Prabhakar
2023-08-31 16:36                 ` Conor Dooley
2023-09-01  8:34                   ` Lad, Prabhakar

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=CA+V-a8thx2qah2gJVG6mmrSCtnLTBRFS7fr+cpTMU-6RpqoaTQ@mail.gmail.com \
    --to=prabhakar.csengg@gmail.com \
    --cc=conor.dooley@microchip.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=palmer@rivosinc.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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