From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Conor Dooley <conor@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: linux-next: Tree for Aug 31 (riscv: ANDES errata)
Date: Thu, 31 Aug 2023 22:33:40 -0700 [thread overview]
Message-ID: <33a5e278-fb4b-b5db-e4f6-bb5a1e4228ef@infradead.org> (raw)
In-Reply-To: <20230831135535.13c67178@canb.auug.org.au>
On 8/30/23 20:55, Stephen Rothwell wrote:
> Hi all,
>
> Please do *not* include material destined for v6.7 in your linux-next
> included branches until *after* v6.6-rc1 has been released. Also,
> do *not* rebase you linu-next included branches onto v6.5.
>
> Changes since 20230830:
>
> The risc-v tree gained conflicts aginst Linus' tree.
>
On risc-v 32-bit or 64-bit, when CONFIG_MMU is not set:
32BIT:
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]
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]
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]
../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;
| ^~~
64BIT:
I don't see the Kconfig warnings, just the error/warning messages from errata.c
--
~Randy
next prev parent reply other threads:[~2023-09-01 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 3:55 linux-next: Tree for Aug 31 Stephen Rothwell
2023-09-01 5:33 ` Randy Dunlap [this message]
2023-09-01 6:23 ` linux-next: Tree for Aug 31 (riscv: ANDES errata) Conor Dooley
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=33a5e278-fb4b-b5db-e4f6-bb5a1e4228ef@infradead.org \
--to=rdunlap@infradead.org \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=sfr@canb.auug.org.au \
/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).