All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "José Roberto de Souza" <jose.souza@intel.com>,
	"Lionel Landwerlin" <lionel.g.landwerlin@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the drm-xe tree
Date: Wed, 11 Mar 2026 13:08:03 +0000	[thread overview]
Message-ID: <abFpM1FHgzgARB88@sirena.org.uk> (raw)

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

Hi all,

After merging the drm-xe tree, today's linux-next build (KCONFIG_NAME)
failed like this:

/tmp/next/build/drivers/gpu/drm/xe/xe_lrc.c: In function 'xe_lrc_ctx_init':
/tmp/next/build/drivers/gpu/drm/xe/xe_lrc.c:1554:43: error: implicit declaration of function '_MASKED_BIT_ENABLE'; did you mean 'REG_MASKED_FIELD_ENABLE'? [-Wimplicit-function-declaration]
 1554 |                 state_cache_perf_fix[2] = _MASKED_BIT_ENABLE(DISABLE_STATE_CACHE_PERF_FIX);
      |                                           ^~~~~~~~~~~~~~~~~~
      |                                           REG_MASKED_FIELD_ENABLE

Caused by commit

  0e07b16371b6e (drm/xe: Allow per queue programming of COMMON_SLICE_CHICKEN3 bit13)

I have used the tree from next-20260310 instead.

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

             reply	other threads:[~2026-03-11 13:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 13:08 Mark Brown [this message]
2026-03-11 17:16 ` linux-next: build failure after merge of the drm-xe tree Souza, Jose
2026-03-11 18:10   ` Rodrigo Vivi
2026-03-11 18:16     ` Souza, Jose
2026-03-11 20:11       ` Rodrigo Vivi
2026-03-12  7:47         ` Lionel Landwerlin
2026-03-12 11:43           ` Mark Brown
2026-03-13  0:50             ` Rodrigo Vivi
2026-03-13  1:18               ` Souza, Jose
2026-03-13 13:25               ` Mark Brown
2026-03-13  0:46           ` Rodrigo Vivi
2026-03-13 13:57           ` Jani Nikula
2026-03-16 17:38             ` Mark Brown
2026-03-19  8:59               ` Jani Nikula
2026-03-19  9:00                 ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2025-03-07  2:21 Stephen Rothwell
2025-03-11  2:15 ` Stephen Rothwell
2025-03-07  1:58 Stephen Rothwell
2025-03-11  2:13 ` Stephen Rothwell
2024-12-04 13:36 Mark Brown
2024-12-04 13:46 ` Jani Nikula
2024-12-04 14:18   ` Mark Brown
2024-10-01  1:38 Stephen Rothwell
2024-02-22  8:04 Stephen Rothwell
2024-02-22 17:09 ` 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=abFpM1FHgzgARB88@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=jose.souza@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lionel.g.landwerlin@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.