From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: intel-gfx@lists.freedesktop.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
intel-xe@lists.freedesktop.org
Subject: Re: linux-next: Tree for Jan 23 (drm/xe/)
Date: Wed, 24 Jan 2024 11:17:44 +0200 [thread overview]
Message-ID: <87le8fks3r.fsf@intel.com> (raw)
In-Reply-To: <152521f9-119f-4c61-b467-3e91f4aecb1a@infradead.org>
On Tue, 23 Jan 2024, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 1/22/24 18:29, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: there will be no linux-next release on Friday
>>
>> Changes since 20240122:
>>
>
> on ARM64, when
> DRM_I915 is not set
> DRM_XE=m
> DEBUG_FS is not set
>
> ../drivers/gpu/drm/i915/display/intel_display_debugfs.c:1091:6: error: redefinition of 'intel_display_debugfs_register'
> 1091 | void intel_display_debugfs_register(struct drm_i915_private *i915)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from ../drivers/gpu/drm/i915/display/intel_display_debugfs.c:19:
Does [1] fix the issue?
BR,
Jani.
[1] https://lore.kernel.org/r/20240124090515.3363901-1-jani.nikula@intel.com
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-24 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 2:29 linux-next: Tree for Jan 23 Stephen Rothwell
2024-01-23 21:52 ` linux-next: Tree for Jan 23 (drm/xe/) Randy Dunlap
2024-01-23 21:52 ` Randy Dunlap
2024-01-24 9:17 ` Jani Nikula [this message]
2024-01-24 21:35 ` Randy Dunlap
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=87le8fks3r.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.