From: Sameer Rahmani <lxsameer@gnu.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust to kobject doc ReST conversion
Date: Wed, 4 Mar 2020 11:57:33 +0000 [thread overview]
Message-ID: <959e8f4c-9ff6-4388-9b6f-23f6e548e9e5@gnu.org> (raw)
In-Reply-To: <20200304110821.7243-1-lukas.bulwahn@gmail.com>
On 04/03/2020 11:08, Lukas Bulwahn wrote:
> Commit 5fed00dcaca8 ("Documentation: kobject.txt has been moved to
> core-api/kobject.rst") missed to adjust the entry in MAINTAINERS.
>
> Since then, ./scripts/get_maintainer.pl --self-test complains:
>
> warning: no file matches F: Documentation/kobject.txt
>
> Adjust DRIVER CORE, KOBJECTS, DEBUGFS AND SYSFS entry in MAINTAINERS.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Sameer, please ack.
> Jonathan, pick pick this patch for doc-next.
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d064049aad1b..998d56e61a41 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5213,7 +5213,7 @@ M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> R: "Rafael J. Wysocki" <rafael@kernel.org>
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
> S: Supported
> -F: Documentation/kobject.txt
> +F: Documentation/core-api/kobject.rst
> F: drivers/base/
> F: fs/debugfs/
> F: fs/sysfs/
Hi Lukas,
Thanks for the fix. It looks good to me
next prev parent reply other threads:[~2020-03-04 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 11:08 [PATCH] MAINTAINERS: adjust to kobject doc ReST conversion Lukas Bulwahn
2020-03-04 11:57 ` Sameer Rahmani [this message]
2020-03-04 21:37 ` Lukas Bulwahn
2020-03-10 17:30 ` Jonathan Corbet
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=959e8f4c-9ff6-4388-9b6f-23f6e548e9e5@gnu.org \
--to=lxsameer@gnu.org \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.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).