From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Benson Leung" <bleung@google.com>,
"Guenter Roeck" <groeck@chromium.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the chrome-platform tree
Date: Mon, 3 Jun 2024 04:20:09 +0000 [thread overview]
Message-ID: <Zl1EefBEvsQgnEZv@google.com> (raw)
In-Reply-To: <20240603132517.7f344f9f@canb.auug.org.au>
On Mon, Jun 03, 2024 at 01:25:36PM +1000, Stephen Rothwell wrote:
> After merging the chrome-platform tree, today's linux-next build
> (htmldocs) produced this warning:
>
> MAINTAINERS:11167: WARNING: unknown document: '../hwmon/chros_ec_hwmon'
>
> Introduced by commit
>
> e8665a172378 ("hwmon: add ChromeOS EC driver")
A typo in the applied patch. Fixed.
next prev parent reply other threads:[~2024-06-03 4:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 3:25 linux-next: build warning after merge of the chrome-platform tree Stephen Rothwell
2024-06-03 4:20 ` Tzung-Bi Shih [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-16 11:38 Stephen Rothwell
2022-05-17 13:09 ` Muhammad Usama Anjum
2022-05-18 3:23 ` Bagas Sanjaya
2022-05-18 3:39 ` Tzung-Bi Shih
2022-05-18 4:24 ` Muhammad Usama Anjum
2021-08-23 5:21 Stephen Rothwell
2021-08-30 7:21 ` Stephen Rothwell
2021-08-31 0:17 ` Benson Leung
2021-08-31 0:32 ` Stephen Rothwell
2019-04-16 4:30 Stephen Rothwell
2019-04-16 9:09 ` Enric Balletbo i Serra
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=Zl1EefBEvsQgnEZv@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=sfr@canb.auug.org.au \
/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