mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: "Thomas Weißschuh" <thomas@weissschuh.net>,
	"Jean Delvare" <jdelvare@suse.com>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Benson Leung" <bleung@chromium.org>,
	chrome-platform@lists.linux.dev, linux-hwmon@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lukas Bulwahn" <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: repair file entry in CHROMEOS EC HARDWARE MONITORING
Date: Mon, 3 Jun 2024 08:01:39 +0000	[thread overview]
Message-ID: <Zl14Y2tia0s-BEht@google.com> (raw)
In-Reply-To: <20240603072352.9396-1-lukas.bulwahn@redhat.com>

On Mon, Jun 03, 2024 at 09:23:43AM +0200, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> 
> Commit e8665a172378 ("hwmon: add ChromeOS EC driver") adds a driver, some
> documentation and the new section CHROMEOS EC HARDWARE MONITORING in
> MAINTAINERS. The commit adds Documentation/hwmon/cros_ec_hwmon.rst. The
> file entry in the MAINTAINERS section however accidentally refers to
> chros_ec_hwmon.rst.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
> 
> Refer to the intended documentation file.

Thanks for your patch.

Received a notification about the error in [1] earlier.  Given that it is a
minor issue, I fixed it directly to the original commit (instead of sending
out an independent patch with Fixes tag).  It should be fixed in the following
linux-next (e.g. next-20240604).

[1]: https://lore.kernel.org/linux-next/20240603132517.7f344f9f@canb.auug.org.au/

      reply	other threads:[~2024-06-03  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  7:23 Lukas Bulwahn
2024-06-03  8:01 ` Tzung-Bi Shih [this message]

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=Zl14Y2tia0s-BEht@google.com \
    --to=tzungbi@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=jdelvare@suse.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lbulwahn@redhat.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lukas.bulwahn@redhat.com \
    --cc=thomas@weissschuh.net \
    /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®