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 DRI Development <dri-devel@lists.freedesktop.org>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: linux-next: Tree for Jun 25 (drivers/gpu/drm/{i915,xe}/intel_pcode.o)
Date: Wed, 25 Jun 2025 20:57:40 -0700 [thread overview]
Message-ID: <3667a992-a24b-4e49-aab2-5ca73f2c0a56@infradead.org> (raw)
In-Reply-To: <20250625172220.2b6aeff8@canb.auug.org.au>
On 6/25/25 12:22 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20250624:
>
on i386, when both CONFIG_DRM_XE=y
and CONFIG_DRM_I915=y:
ld: drivers/gpu/drm/xe/xe_pcode.o: in function `intel_pcode_read':
xe_pcode.c:(.text+0x7d0): multiple definition of `intel_pcode_read'; drivers/gpu/drm/i915/intel_pcode.o:intel_pcode.c:(.text+0x990): first defined here
ld: drivers/gpu/drm/xe/xe_pcode.o: in function `intel_pcode_write_timeout':
xe_pcode.c:(.text+0x850): multiple definition of `intel_pcode_write_timeout'; drivers/gpu/drm/i915/intel_pcode.o:intel_pcode.c:(.text+0x9b0): first defined here
ld: drivers/gpu/drm/xe/xe_pcode.o: in function `intel_pcode_request':
xe_pcode.c:(.text+0x8f0): multiple definition of `intel_pcode_request'; drivers/gpu/drm/i915/intel_pcode.o:intel_pcode.c:(.text+0x9d0): first defined here
--
~Randy
next prev parent reply other threads:[~2025-06-26 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 7:22 linux-next: Tree for Jun 25 Stephen Rothwell
2025-06-26 3:57 ` Randy Dunlap [this message]
2025-06-26 19:15 ` linux-next: Tree for Jun 25 (drivers/gpu/drm/{i915,xe}/intel_pcode.o) Lucas De Marchi
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=3667a992-a24b-4e49-aab2-5ca73f2c0a56@infradead.org \
--to=rdunlap@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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