[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1603792384.git.mchehab+huawei@kernel.org>
Date: Tue, 27 Oct 2020 11:20:35 +0100
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Linux Doc Mailing List <linux-doc@...r.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>
Subject: [PATCH v4 0/2] kernel-doc: fix typedef function parser
Hi Jon,
This small series contain the latest version of the typedef parsing
fixes that we've been discussing as:
[PATCH v3 01/56] scripts: kernel-doc: fix typedef parsing
As I said there, at least while discussing it, I opted to split the
patch in two.
The first one changes the regex;
The second one is just a cleanup that splits the 3 arguments into 3
vars.
>From my side, I'm not 100% confident if the second patch is
worth or not.
The advantage of it is that it makes easier to read the regex.
It also also makes clearer about the differences between
the two typedef regex'es that are used there.
On the other hand, using a site like regex101.com to
test it is harder, as one needs to copy-and-paste 3 expressions
instead of just one.
So, when appliying, feel free to decide to either:
- merge both as-is (two separate patches);
- fold them into a single patch;
- drop the second patch.
Mauro Carvalho Chehab (2):
scripts: kernel-doc: fix typedef parsing
scripts: kernel-doc: split typedef complex regex
scripts/kernel-doc | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
--
2.26.2
Powered by blists - more mailing lists