From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org,
arkadiusz.kubalewski@intel.com, jiri@resnulli.us
Subject: Re: [PATCH net] MAINTAINERS: make the DPLL entry cover drivers
Date: Tue, 16 Sep 2025 09:40:49 +0100 [thread overview]
Message-ID: <d0362eae-cd2f-4a83-a953-d2bbeae36857@linux.dev> (raw)
In-Reply-To: <20250915234255.1306612-1-kuba@kernel.org>
On 16.09.2025 00:42, Jakub Kicinski wrote:
> DPLL maintainers should probably be CCed on driver patches, too.
> Remove the *, which makes the pattern only match files directly
> under drivers/dpll but not its sub-directories.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: vadim.fedorenko@linux.dev
> CC: arkadiusz.kubalewski@intel.com
> CC: jiri@resnulli.us
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 47bc35743f22..4b2ef595c764 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7431,7 +7431,7 @@ S: Supported
> F: Documentation/devicetree/bindings/dpll/dpll-device.yaml
> F: Documentation/devicetree/bindings/dpll/dpll-pin.yaml
> F: Documentation/driver-api/dpll.rst
> -F: drivers/dpll/*
> +F: drivers/dpll/
> F: include/linux/dpll.h
> F: include/uapi/linux/dpll.h
Acked-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2025-09-16 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 23:42 [PATCH net] MAINTAINERS: make the DPLL entry cover drivers Jakub Kicinski
2025-09-16 8:08 ` Jiri Pirko
2025-09-16 8:40 ` Vadim Fedorenko [this message]
2025-09-16 8:43 ` Kubalewski, Arkadiusz
2025-09-17 0:20 ` patchwork-bot+netdevbpf
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=d0362eae-cd2f-4a83-a953-d2bbeae36857@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).