From: Thierry Reding <thierry.reding@gmail.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Thomas Zimmermann <tzimmermann@suse.de>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] arch/powerpc: Add missing includes
Date: Wed, 29 Oct 2025 16:09:38 +0100 [thread overview]
Message-ID: <20251029150940.2523328-1-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding@nvidia.com>
Hi,
I've recently been doing a few test builds for some of the more exotic
platforms out there for a patch series that I'm working on and ran into
some issues that seem to have been caused by the framebuffer include
rework. I see that Thomas did address some of those already, but it
looks like I've been running with slightly different configurations or
something that caused these additional ones to come up.
Given that theese seem to have been broken for more than a year and it's
not exactly clear which commit it caused, I didn't bother adding a Fixes
line, but still wanted to send these out in case we want to keep these
platforms building.
Thierry
Thierry Reding (2):
arch/powerpc: Add missing linux/of.h include
macintosh/via-pmu-backlight: Include uapi/linux/fb.h
arch/powerpc/platforms/powermac/backlight.c | 1 +
drivers/macintosh/via-pmu-backlight.c | 1 +
2 files changed, 2 insertions(+)
--
2.51.0
next reply other threads:[~2025-10-29 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 15:09 Thierry Reding [this message]
2025-10-29 15:09 ` [PATCH 1/2] arch/powerpc: Add missing linux/of.h include Thierry Reding
2025-10-29 15:09 ` [PATCH 2/2] macintosh/via-pmu-backlight: Include uapi/linux/fb.h Thierry Reding
2025-10-29 20:27 ` [PATCH 0/2] arch/powerpc: Add missing includes Thomas Zimmermann
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=20251029150940.2523328-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=tzimmermann@suse.de \
/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