Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>,
	Linus Walleij <linusw@kernel.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 in the final build
Date: Wed, 10 Jun 2026 16:51:57 +0100	[thread overview]
Message-ID: <aimIHT8KI0LZNERH@sirena.co.uk> (raw)

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

Hi all,

In the final build, today's linux-next build (arm64 allyesconfig)
failed like this:

/tmp/next/build/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c:82:12: error: 'lpi_gpio_write' defined but not used [-Werror=unused-function]
   82 | static int lpi_gpio_write(struct lpi_pinctrl *state, unsigned int pin,
      |            ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors make[6]:

The failure also shows up in a defconfig build but that doesn't enable
-Werror.  I have ignored this issue for today.

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

             reply	other threads:[~2026-06-10 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 15:51 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-21 17:14 linux-next: build failure in the final build Mark Brown
2026-01-21 17:18 ` Miguel Ojeda
2026-01-21 17:24   ` Mark Brown
2026-01-21 18:14     ` Miguel Ojeda
2026-01-21 19:14 ` Alice Ryhl
2026-01-21 19:24   ` Miguel Ojeda
2026-01-22 11:20     ` Mark Brown
2026-01-22  0:42   ` Deborah Brouwer
2026-01-22 11:17   ` Mark Brown

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=aimIHT8KI0LZNERH@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=ajay.nandam@oss.qualcomm.com \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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