Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Pan Chuang <panchuang@vivo.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 thunderbolt tree
Date: Mon, 27 Jul 2026 16:04:17 +0100	[thread overview]
Message-ID: <amdzcQ97eSeOg9C_@sirena.org.uk> (raw)

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

Hi all,

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

/tmp/next/build/drivers/thunderbolt/pci.c:115:17: error: unused variable 'dev' [-Werror,-Wunused-variable]
  115 |         struct device *dev = &pdev->dev;
      |                        ^~~
1 error generated.  make[5]: ***

Caused by commit

   eef9f6d8c36f7 (thunderbolt: Remove redundant dev_err_probe())

I have used the tree from next-20260726 instead.

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

             reply	other threads:[~2026-07-27 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 15:04 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-30  6:03 linux-next: build failure after merge of the thunderbolt tree Stephen Rothwell
2020-06-30  9:27 ` Alan Maguire
2020-06-30 11:33 ` Mika Westerberg
2020-08-09  0:50   ` Guenter Roeck
2020-08-09  8:18 ` Stephen Rothwell
2020-08-09 18:04   ` Linus Torvalds
2020-08-09 23:10     ` Stephen Rothwell
2020-08-10 10:12       ` Mika Westerberg

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=amdzcQ97eSeOg9C_@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=panchuang@vivo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox