From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
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 pwrseq tree
Date: Wed, 26 Aug 2026 14:06:55 +0100 [thread overview]
Message-ID: <ao7k768ba0JAB1-9@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Hi all,
After merging the pwrseq tree, today's linux-next build (arm64
defconfig) failed like this:
/tmp/next/build/drivers/bluetooth/btnxpuart.c: In function 'nxp_serdev_probe':
/tmp/next/build/drivers/bluetooth/btnxpuart.c:1906:23: error: implicit declaration of function 'pwrseq_power_on' [-Wimplicit-function-declaration]
1906 | err = pwrseq_power_on(pwrseq);
| ^~~~~~~~~~~~~~~
Caused by commit
d51fc9d4cd6eb (power: sequencing: rename pwrseq_power_on/off() to pwrseq_enable/disable())
which is based on v7.2-rc1 and hence misses things that already went in
during the merge window. Rather than fix this up as a semantic conflict
I've merged the version from next-20260825, this really doesn't feel
like something that should be added during the merge window.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-08-26 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ao7k768ba0JAB1-9@sirena.org.uk \
--to=broonie@kernel.org \
--cc=brgl@bgdev.pl \
--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
all inboxes | Powered by JetHome®