From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Martin KaFai Lau <kafai@fb.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Two fixes for documentation-file-ref-check
Date: Tue, 26 Oct 2021 09:42:52 -0600 [thread overview]
Message-ID: <875ytjg5c3.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1634629094.git.mchehab+huawei@kernel.org>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Hi Jon,
>
> This small series contain two fixes for documentation-file-ref-check,
> in order to remove some (false) positives.
>
> The first one makes it to ignore files that start with a dot. It
> prevents the script to try parsing hidden files.
>
> The second one shuts up (currently) two false-positives for some
> documents under:
>
> tools/bpf/bpftool/Documentation/
>
> Mauro Carvalho Chehab (2):
> scripts: documentation-file-ref-check: ignore hidden files
> scripts: documentation-file-ref-check: fix bpf selftests path
>
> scripts/documentation-file-ref-check | 4 ++++
> 1 file changed, 4 insertions(+)
Set applied, thanks.
jon
prev parent reply other threads:[~2021-10-26 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 7:42 [PATCH 0/2] Two fixes for documentation-file-ref-check Mauro Carvalho Chehab
2021-10-19 7:42 ` [PATCH 2/2] scripts: documentation-file-ref-check: fix bpf selftests path Mauro Carvalho Chehab
2021-10-26 15:42 ` Jonathan Corbet [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=875ytjg5c3.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).