Linux-Next discussions
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: linux-next: Tree for Oct 27 (drivers/cache/ax45mp_cache.o)
Date: Mon, 30 Oct 2023 11:09:39 +0000	[thread overview]
Message-ID: <20231030-overhand-brittle-b2c4dc7ad4e6@spud> (raw)
In-Reply-To: <a7fe0eca-2a18-41b1-a0a9-e54a6e49903b@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

On Sun, Oct 29, 2023 at 10:17:35PM -0700, Randy Dunlap wrote:
> 
> 
> On 10/29/23 22:12, Randy Dunlap wrote:
> > 
> > 
> > On 10/27/23 00:04, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Changes since 20231026:
> >>
> > 
> > on riscv32:
> > 
> > riscv32-linux-ld: drivers/cache/ax45mp_cache.o: in function `ax45mp_cache_init':
> > ax45mp_cache.c:(.init.text+0xe4): undefined reference to `riscv_noncoherent_register_cache_ops'
> > 
> > Full randconfig file is attached.
> > 
> 
> or with a different config file:
> 
> iscv32-linux-ld: arch/riscv/mm/pmem.o:(.text+0xa): undefined reference to `noncoherent_cache_ops'
> riscv32-linux-ld: arch/riscv/mm/pmem.o:(.text+0xe): undefined reference to `noncoherent_cache_ops'
> riscv32-linux-ld: arch/riscv/mm/pmem.o: in function `.L6':
> pmem.c:(.text+0x8a): undefined reference to `noncoherent_cache_ops'
> riscv32-linux-ld: pmem.c:(.text+0x8e): undefined reference to `noncoherent_cache_ops'
> riscv32-linux-ld: drivers/cache/ax45mp_cache.o: in function `.L26':
> ax45mp_cache.c:(.init.text+0xd8): undefined reference to `riscv_noncoherent_register_cache_ops'
> 
> and that randconfig file is attached.
> 
> I also have this one on riscv64:
> 
> riscv64-linux-ld: arch/riscv/mm/pmem.o: in function `arch_wb_cache_pmem':
> pmem.c:(.text+0x20): undefined reference to `noncoherent_cache_ops'
> riscv64-linux-ld: arch/riscv/mm/pmem.o: in function `arch_invalidate_pmem':
> pmem.c:(.text+0xcc): undefined reference to `noncoherent_cache_ops'
> riscv64-linux-ld: drivers/cache/ax45mp_cache.o: in function `.L30':
> ax45mp_cache.c:(.init.text+0x174): undefined reference to `riscv_noncoherent_register_cache_ops'
> 
> LMK if anyone wants the .config file for that one.

I think Christoph has already posted a fix for that one:
https://lore.kernel.org/all/20231028155101.1039049-1-hch@lst.de/

I'll look at the other one, if Prabhakar doesn't beat me to it.

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-10-30 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  7:04 linux-next: Tree for Oct 27 Stephen Rothwell
2023-10-30  5:12 ` linux-next: Tree for Oct 27 (drivers/cache/ax45mp_cache.o) Randy Dunlap
2023-10-30  5:17   ` Randy Dunlap
2023-10-30 11:09     ` Conor Dooley [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=20231030-overhand-brittle-b2c4dc7ad4e6@spud \
    --to=conor@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=rdunlap@infradead.org \
    --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