From: Willy Tarreau <w@1wt.eu>
To: Joe Perches <joe@perches.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
LukasBulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-riscv@lists.infradead.org, netdev@vger.kernel.org,
linux-csky@vger.kernel.org
Subject: Re: What is the oldest perl version being used with the kernel ? update oldest supported to 5.14 ?
Date: Fri, 20 Aug 2021 19:33:36 +0200 [thread overview]
Message-ID: <20210820173336.GA26130@1wt.eu> (raw)
In-Reply-To: <37ec9a36a5f7c71a8e23ab45fd3b7f20efd5da24.camel@perches.com>
On Fri, Aug 20, 2021 at 10:27:59AM -0700, Joe Perches wrote:
> Perl 5.8 is nearly 20 years old now.
>
> https://en.wikipedia.org/wiki/Perl_5_version_history
>
> checkpatch uses regexes that are incompatible with perl versions
> earlier than 5.10, but these uses are currently runtime checked
> and skipped if the perl version is too old. This runtime checking
> skips several useful tests.
>
> There is also some desire for tools like kernel-doc, checkpatch and
> get_maintainer to use a common library of regexes and functions:
> https://lore.kernel.org/lkml/YR2lexDd9N0sWxIW@casper.infradead.org/
>
> It'd be useful to set the minimum perl version to something more modern.
>
> I believe perl 5.14, now only a decade old, is a reasonable target.
>
> Any objections or suggestions for a newer minimum version?
It's probably reasonable, even the Slackware 14.2 on my home PC, which
is starting to date, ships a 5.22.
Willy
WARNING: multiple messages have this Message-ID (diff)
From: Willy Tarreau <w@1wt.eu>
To: Joe Perches <joe@perches.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
LukasBulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-riscv@lists.infradead.org, netdev@vger.kernel.org,
linux-csky@vger.kernel.org
Subject: Re: What is the oldest perl version being used with the kernel ? update oldest supported to 5.14 ?
Date: Fri, 20 Aug 2021 19:33:36 +0200 [thread overview]
Message-ID: <20210820173336.GA26130@1wt.eu> (raw)
In-Reply-To: <37ec9a36a5f7c71a8e23ab45fd3b7f20efd5da24.camel@perches.com>
On Fri, Aug 20, 2021 at 10:27:59AM -0700, Joe Perches wrote:
> Perl 5.8 is nearly 20 years old now.
>
> https://en.wikipedia.org/wiki/Perl_5_version_history
>
> checkpatch uses regexes that are incompatible with perl versions
> earlier than 5.10, but these uses are currently runtime checked
> and skipped if the perl version is too old. This runtime checking
> skips several useful tests.
>
> There is also some desire for tools like kernel-doc, checkpatch and
> get_maintainer to use a common library of regexes and functions:
> https://lore.kernel.org/lkml/YR2lexDd9N0sWxIW@casper.infradead.org/
>
> It'd be useful to set the minimum perl version to something more modern.
>
> I believe perl 5.14, now only a decade old, is a reasonable target.
>
> Any objections or suggestions for a newer minimum version?
It's probably reasonable, even the Slackware 14.2 on my home PC, which
is starting to date, ships a 5.22.
Willy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-08-20 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 17:27 What is the oldest perl version being used with the kernel ? update oldest supported to 5.14 ? Joe Perches
2021-08-20 17:27 ` Joe Perches
2021-08-20 17:33 ` Willy Tarreau [this message]
2021-08-20 17:33 ` Willy Tarreau
2021-08-20 18:25 ` Matthew Wilcox
2021-08-20 18:25 ` Matthew Wilcox
2021-08-21 5:43 ` Kees Cook
2021-08-21 5:43 ` Kees Cook
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=20210820173336.GA26130@1wt.eu \
--to=w@1wt.eu \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-csky@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=willy@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 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.