From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the fsl tree
Date: Sat, 11 Jul 2026 09:45:35 +0200 [thread overview]
Message-ID: <e05a4ef1-af8f-4525-9747-08531948ea36@kernel.org> (raw)
In-Reply-To: <alDgvHf9mKOJI1cc@sirena.org.uk>
Le 10/07/2026 à 14:08, Mark Brown a écrit :
> Hi all,
>
> After merging the fsl tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
...
>
> Caused by commit
>
> 4b265b93b4e0e (powerpc: Move CONFIG_QE_GPIO to SoC)
>
> I have used the tree from next-20260709 instead.
Thanks for letting me know. I have dropped this patch for now.
CONFIG_USB_FHCI_HCD depends on CONFIG_QE_GPIO but uses in_be16() etc ...
helpers which are powerpc specific, so dependency to PPC needs to be
kept for now.
Christophe
next prev parent reply other threads:[~2026-07-11 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 12:08 Mark Brown
2026-07-11 7:45 ` Christophe Leroy (CS GROUP) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-18 0:47 Stephen Rothwell
2014-05-12 5:55 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=e05a4ef1-af8f-4525-9747-08531948ea36@kernel.org \
--to=chleroy@kernel.org \
--cc=broonie@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
Powered by JetHome