X86 platform drivers
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <mark.gross@intel.com>,
	Gayatri Kammela <gayatri.kammela@intel.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Rajneesh Bhardwaj <irenic.rajneesh@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org
Subject: linux-next: build failure after merge of the drivers-x86 tree
Date: Wed, 28 Jul 2021 17:48:47 +0100	[thread overview]
Message-ID: <20210728164847.46855-1-broonie@kernel.org> (raw)

Hi all,

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

error: the following would cause module name conflict:
  drivers/misc/c2port/core.ko
  drivers/platform/x86/intel/pmc/core.ko

Caused by commit

  29036fcc92b22d ("platform/x86/intel: intel_pmc_core: Move intel_pmc_core* files to pmc subfolder")

Since there was nothing in the branch yesterday I've just dropped the
tree entirely.

             reply	other threads:[~2021-07-28 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 16:48 Mark Brown [this message]
2021-07-28 17:01 ` linux-next: build failure after merge of the drivers-x86 tree Andy Shevchenko
2021-07-28 17:27   ` Kammela, Gayatri
2021-07-28 17:55     ` Hans de Goede
2021-07-28 17:59       ` Kammela, Gayatri
     [not found] <20250515164620.071d70e3@canb.auug.org.au>
2025-05-15  8:32 ` Ilpo Järvinen
2025-05-15  9:22   ` Ingo Molnar
2025-05-15 12:19     ` Stephen Rothwell
2025-05-15 12:57       ` Ingo Molnar
     [not found] <20110222162206.c3fb0636.sfr@canb.auug.org.au>
     [not found] ` <a8c6f32c-ccb5-4f65-b537-8bd1c11f7336@email.android.com>
2011-02-22 11:46   ` Mattia Dongili
2011-02-22 14:34     ` Matthew Garrett
2011-02-22 22:22       ` Stephen Rothwell

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=20210728164847.46855-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=gayatri.kammela@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=irenic.rajneesh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mark.gross@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /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