public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Neal Liu <neal_liu@aspeedtech.com>,
	linux-aspeed@lists.ozlabs.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] MAINTAINERS: Repair file entry in ASPEED USB UDC DRIVER
Date: Wed, 15 Jun 2022 21:44:09 +0200	[thread overview]
Message-ID: <20220615194409.11875-1-lukas.bulwahn@gmail.com> (raw)

Commit 055276c13205 ("usb: gadget: add Aspeed ast2600 udc driver") adds
the section ASPEED USB UDC DRIVER with a file entry to aspeed,udc.yaml,
but then, commit 0dde9a46a2cf ("dt-bindings: usb: add documentation for
aspeed udc") actually adds a device tree binding aspeed,ast2600-udc.yaml.

Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
broken reference.

Repair the reference to the actually added file in ASPEED USB UDC DRIVER.

Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
Neal, please ack.
Greg, please pick this minor non-urgent clean-up patch in your usb-next tree.

 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index d9c3576b082f..8830d1adb23b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3144,7 +3144,7 @@ ASPEED USB UDC DRIVER
 M:	Neal Liu <neal_liu@aspeedtech.com>
 L:	linux-aspeed@lists.ozlabs.org (moderated for non-subscribers)
 S:	Maintained
-F:	Documentation/devicetree/bindings/usb/aspeed,udc.yaml
+F:	Documentation/devicetree/bindings/usb/aspeed,ast2600-udc.yaml
 F:	drivers/usb/gadget/udc/aspeed_udc.c
 
 ASUS NOTEBOOKS AND EEEPC ACPI/WMI EXTRAS DRIVERS
-- 
2.17.1


             reply	other threads:[~2022-06-15 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 19:44 Lukas Bulwahn [this message]
2022-06-16  1:16 ` [PATCH] MAINTAINERS: Repair file entry in ASPEED USB UDC DRIVER Neal Liu

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=20220615194409.11875-1-lukas.bulwahn@gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=neal_liu@aspeedtech.com \
    /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