netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	Jiri Pirko <jiri@resnulli.us>,
	netdev@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust header file entry in DPLL SUBSYSTEM
Date: Mon, 25 Sep 2023 09:09:01 +0100	[thread overview]
Message-ID: <0b1ffbb6-12a6-22eb-f197-4a8f3bd2074c@linux.dev> (raw)
In-Reply-To: <20230925054305.16771-1-lukas.bulwahn@gmail.com>

On 25/09/2023 06:43, Lukas Bulwahn wrote:
> Commit 9431063ad323 ("dpll: core: Add DPLL framework base functions") adds
> the section DPLL SUBSYSTEM in MAINTAINERS and includes a file entry to the
> non-existing file 'include/net/dpll.h'.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference. Looking at the file stat of the commit above, this entry
> clearly intended to refer to 'include/linux/dpll.h'.
> 
> Adjust this header file entry in DPLL SUBSYSTEM.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
>   MAINTAINERS | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9aa84682ccb9..cfa82f0fe017 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6363,7 +6363,7 @@ L:	netdev@vger.kernel.org
>   S:	Supported
>   F:	Documentation/driver-api/dpll.rst
>   F:	drivers/dpll/*
> -F:	include/net/dpll.h
> +F:	include/linux/dpll.h
>   F:	include/uapi/linux/dpll.h
>   
>   DRBD DRIVER

Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>

      reply	other threads:[~2023-09-25  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  5:43 [PATCH] MAINTAINERS: adjust header file entry in DPLL SUBSYSTEM Lukas Bulwahn
2023-09-25  8:09 ` Vadim Fedorenko [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=0b1ffbb6-12a6-22eb-f197-4a8f3bd2074c@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=netdev@vger.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 NNTP newsgroup(s).