All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"DRM XE List" <intel-xe@lists.freedesktop.org>
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, 4 Dec 2024 13:36:02 +0000	[thread overview]
Message-ID: <Z1BawrcFMsj0ByLk@sirena.org.uk> (raw)

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

Hi all,

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

In file included from /tmp/next/build/include/linux/module.h:22,
                 from /tmp/next/build/include/linux/device/driver.h:21,
                 from /tmp/next/build/include/linux/device.h:32,
                 from /tmp/next/build/include/linux/auxiliary_bus.h:11,
                 from /tmp/next/build/include/linux/intel_vsec.h:5,
                 from /tmp/next/build/drivers/gpu/drm/xe/xe_vsec.c:7:
/tmp/next/build/drivers/gpu/drm/xe/xe_vsec.c:233:18: error: expected ',' or ';' before 'INTEL_VSEC'
  233 | MODULE_IMPORT_NS(INTEL_VSEC);
      |                  ^~~~~~~~~~
/tmp/next/build/include/linux/moduleparam.h:26:61: note: in definition of macro '__MODULE_INFO'
   26 |                 = __MODULE_INFO_PREFIX __stringify(tag) "=" info
      |                                                             ^~~~
/tmp/next/build/include/linux/module.h:299:33: note: in expansion of macro 'MODULE_INFO'
  299 | #define MODULE_IMPORT_NS(ns)    MODULE_INFO(import_ns, ns)
      |                                 ^~~~~~~~~~~
/tmp/next/build/drivers/gpu/drm/xe/xe_vsec.c:233:1: note: in expansion of macro 'MODULE_IMPORT_NS'
  233 | MODULE_IMPORT_NS(INTEL_VSEC);
      | ^~~~~~~~~~~~~~~~

You need to merge up cdd30ebb1b9f36159d66f088b61aee264e649d7a ("module:
Convert symbol namespace to string literal") from mainline and fix up
for the changes in MODULE_IMPORT_NS.  I'll apply a fixup for now.

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

             reply	other threads:[~2024-12-04 13:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 13:36 Mark Brown [this message]
2024-12-04 13:46 ` linux-next: build failure after merge of the drm-xe tree Jani Nikula
2024-12-04 14:18   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2026-03-11 13:08 Mark Brown
2026-03-11 17:16 ` 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
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-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=Z1BawrcFMsj0ByLk@sirena.org.uk \
    --to=broonie@kernel.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=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.