linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Gaurav Batra <gbatra@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: Tree for Feb 14 (arch/powerpc/platforms/pseries/pci_dlpar.o)
Date: Wed, 14 Feb 2024 18:50:14 -0800	[thread overview]
Message-ID: <c501ff0a-170b-42a8-a5b7-623ebb6c7fba@infradead.org> (raw)
In-Reply-To: <20240214151426.0a398cf0@canb.auug.org.au>

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



On 2/13/24 20:14, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20240213:
> 

on powerpc64:
when CONFIG_IOMMU_API is not set.


powerpc64-linux-ld: arch/powerpc/platforms/pseries/pci_dlpar.o: in function `init_phb_dynamic':
pci_dlpar.c:(.text+0xc4): undefined reference to `ppc_iommu_register_device'
powerpc64-linux-ld: arch/powerpc/platforms/pseries/pci_dlpar.o: in function `remove_phb_dynamic':
pci_dlpar.c:(.text+0x248): undefined reference to `ppc_iommu_unregister_device'


Full randconfig file is attached.

-- 
#Randy

[-- Attachment #2: ppc64-dlpar-iommu-undef.config.gz --]
[-- Type: application/gzip, Size: 34778 bytes --]

  reply	other threads:[~2024-02-15  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  4:14 linux-next: Tree for Feb 14 Stephen Rothwell
2024-02-15  2:50 ` Randy Dunlap [this message]
2024-02-15  3:36   ` linux-next: Tree for Feb 14 (arch/powerpc/platforms/pseries/pci_dlpar.o) Michael Ellerman

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=c501ff0a-170b-42a8-a5b7-623ebb6c7fba@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=gbatra@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --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).