From: "Tomasz Warniełło" <tomasz.warniello@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: kernel-doc: Check existence of FILE arg
Date: Wed, 23 Feb 2022 15:17:02 +0100 [thread overview]
Message-ID: <20220223151702.55a3a7a5@fuji.fritz.box> (raw)
In-Reply-To: <721f860a-a662-0f0c-a82d-eacf80841eb3@gmail.com>
On Wed, 23 Feb 2022 22:59:01 +0900
Akira Yokosawa <akiyks@gmail.com> wrote:
> On Wed, 23 Feb 2022 14:47:13 +0100,
> Tomasz Warniełło wrote:
> > On Wed, 23 Feb 2022 15:07:30 +0900
> > Akira Yokosawa <akiyks@gmail.com> wrote:
> >
> >> Currently, when no FILE argument is given following switches such
> >> as -man, -rst, and -none, kernel-doc ends up in the error of (long
> >> msg from perl folded):
> >>
> >> Use of uninitialized value $ARGV[0] in pattern match (m//)
> >> at ./scripts/kernel-doc line 438.
> >
> > It's a warning not an error.
>
> Good catch!
>
> Will amend in v2 with proper attribution.
>
> Thanks Akira
I'd include this in a series regulating all the CLI syntax - all those
mutual exclusions and arg parsing error handling, etc. At the moment they
exist only in the documentation.
But I'm not sure this is the right moment to do this. Have you seen
my RFC thread? I'd wait until the water stabilises and see the result.
This script may be phased out - how soon, I don't know. Unless you want
to do this purely for sport.
Tomasz
next prev parent reply other threads:[~2022-02-23 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 6:07 [PATCH] scripts: kernel-doc: Check existence of FILE arg Akira Yokosawa
2022-02-23 13:47 ` Tomasz Warniełło
2022-02-23 13:59 ` Akira Yokosawa
2022-02-23 14:17 ` Tomasz Warniełło [this message]
2022-02-23 14:36 ` 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=20220223151702.55a3a7a5@fuji.fritz.box \
--to=tomasz.warniello@gmail.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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