From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: patchwork-bot+chrome-platform@kernel.org,
Tzung-Bi Shih <tzungbi@kernel.org>,
Benson Leung <bleung@chromium.org>
Cc: linux-pwm@vger.kernel.org, chrome-platform@lists.linux.dev
Subject: Re: [PATCH] pwm: Explicitly include correct DT includes
Date: Mon, 11 Sep 2023 09:19:21 +0200 [thread overview]
Message-ID: <20230911071921.6dhadiqmfpedqxvy@pengutronix.de> (raw)
In-Reply-To: <169440670019.22573.2422972280084635660.git-patchwork-notify@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
Hello,
On Mon, Sep 11, 2023 at 04:31:40AM +0000, patchwork-bot+chrome-platform@kernel.org wrote:
> This patch was applied to chrome-platform/linux.git (for-kernelci)
> by Thierry Reding <thierry.reding@gmail.com>:
>
> On Fri, 14 Jul 2023 11:48:50 -0600 you wrote:
> > The DT of_device.h and of_platform.h date back to the separate
> > of_platform_bus_type before it as merged into the regular platform bus.
> > As part of that merge prepping Arm DT support 13 years ago, they
> > "temporarily" include each other. They also include platform_device.h
> > and of.h. As a result, there's a pretty much random mix of those include
> > files used throughout the tree. In order to detangle these headers and
> > replace the implicit includes with struct declarations, users need to
> > explicitly include the correct includes.
> >
> > [...]
>
> Here is the summary with links:
> - pwm: Explicitly include correct DT includes
> https://git.kernel.org/chrome-platform/c/0a41b0c5d97a
>
> You are awesome, thank you!
It's a bit strange to get this notification given that this patch was
applied via the pwm tree and only made it into the
chrome-platform/linux.git repo via an update to v6.6-rc1.
It's not a big problem, but if such mail could be suppressed that would
be nice.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-11 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 17:48 [PATCH] pwm: Explicitly include correct DT includes Rob Herring
2023-07-17 4:01 ` Tzung-Bi Shih
2023-07-17 7:43 ` Uwe Kleine-König
2023-07-17 15:59 ` Rob Herring
2023-07-17 22:39 ` nobuhiro1.iwamatsu
2023-07-20 14:41 ` Thierry Reding
2023-09-11 4:31 ` patchwork-bot+chrome-platform
2023-09-11 7:19 ` Uwe Kleine-König [this message]
2023-09-11 4:49 ` patchwork-bot+chrome-platform
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=20230911071921.6dhadiqmfpedqxvy@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=linux-pwm@vger.kernel.org \
--cc=patchwork-bot+chrome-platform@kernel.org \
--cc=tzungbi@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).