From: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Subject: Re: [PATCH] MAINTAINERS: adjust kprobes.rst entry to new location
Date: Sun, 26 Jul 2020 23:25:07 +0530 [thread overview]
Message-ID: <1595786005.wgos31p5yh.naveen@linux.ibm.com> (raw)
In-Reply-To: <20200726055843.10783-1-lukas.bulwahn@gmail.com>
Lukas Bulwahn wrote:
> Commit 2165b82fde82 ("docs: Move kprobes.rst from staging/ to trace/")
> moved kprobes.rst, but missed to adjust the MAINTAINERS entry.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file matches F: Documentation/staging/kprobes.rst
>
> Adjust the entry to the new file location.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Naveen, Masami-san, please ack.
> Jonathan, please pick this minor non-urgent patch into docs-next.
>
> applies cleanly on next-20200724
Ah, sorry. Hadn't noticed this change from Mauro.
Acked-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Thanks!
- Naveen
WARNING: multiple messages have this Message-ID (diff)
From: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Subject: Re: [PATCH] MAINTAINERS: adjust kprobes.rst entry to new location
Date: Sun, 26 Jul 2020 17:55:39 +0000 [thread overview]
Message-ID: <1595786005.wgos31p5yh.naveen@linux.ibm.com> (raw)
In-Reply-To: <20200726055843.10783-1-lukas.bulwahn@gmail.com>
Lukas Bulwahn wrote:
> Commit 2165b82fde82 ("docs: Move kprobes.rst from staging/ to trace/")
> moved kprobes.rst, but missed to adjust the MAINTAINERS entry.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file matches F: Documentation/staging/kprobes.rst
>
> Adjust the entry to the new file location.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Naveen, Masami-san, please ack.
> Jonathan, please pick this minor non-urgent patch into docs-next.
>
> applies cleanly on next-20200724
Ah, sorry. Hadn't noticed this change from Mauro.
Acked-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Thanks!
- Naveen
next prev parent reply other threads:[~2020-07-26 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 5:58 [PATCH] MAINTAINERS: adjust kprobes.rst entry to new location Lukas Bulwahn
2020-07-26 5:58 ` Lukas Bulwahn
2020-07-26 17:55 ` Naveen N. Rao [this message]
2020-07-26 17:55 ` Naveen N. Rao
2020-07-27 22:22 ` Jonathan Corbet
2020-07-27 22:22 ` Jonathan Corbet
2020-07-28 5:12 ` Masami Hiramatsu
2020-07-28 5:12 ` Masami Hiramatsu
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=1595786005.wgos31p5yh.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.ibm.com \
--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=mhiramat@kernel.org \
--cc=pia.eichinger@st.oth-regensburg.de \
--cc=ralf.ramsauer@oth-regensburg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.