From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Matthew Brost" <matthew.brost@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Christian König" <christian.koenig@amd.com>,
"Somalapuram Amaranath" <Amaranath.Somalapuram@amd.com>,
"Intel Graphics" <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Dave Airlie" <airlied@gmail.com>,
intel-xe@lists.freedesktop.org
Subject: Re: Re: linux-next: build failure after merge of the drm-misc tree
Date: Wed, 07 Feb 2024 11:33:34 +0200 [thread overview]
Message-ID: <87il30d3f5.fsf@intel.com> (raw)
In-Reply-To: <5b3adb702cfaa944fdaa1b49ee7f10e4d0e86b2f.camel@linux.intel.com>
On Wed, 07 Feb 2024, Thomas Hellström <thomas.hellstrom@linux.intel.com> wrote:
> Indeed. Not even drm-misc itself compiles with xe enabled. I'll ping
> drm-misc maintainers.
We'll need CONFIG_DRM_XE=m enabled in drm-rerere/drm-misc-*_defconfig,
and get people to use that.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-07 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 1:28 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2024-02-06 1:28 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2024-02-06 11:46 ` Jani Nikula
2024-02-06 12:39 ` Thomas Hellström
2024-02-06 20:21 ` Lucas De Marchi
2024-02-07 6:56 ` Thomas Hellström
2024-02-07 9:33 ` Jani Nikula [this message]
2024-02-07 2:46 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-07-15 3:55 Stephen Rothwell
2025-07-15 5:51 ` Andy Yan
2021-10-12 2:18 [Intel-gfx] linux-next: " Stephen Rothwell
2021-10-14 3:02 ` luo.penghao
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=87il30d3f5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Amaranath.Somalapuram@amd.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--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=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas.hellstrom@linux.intel.com \
/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.