Linux CXL
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Alison Schofield <alison.schofield@intel.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: Alison Schofield <alison.schofield@intel.com>,
	linux-doc@vger.kernel.org, linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2 1/2] docs: python: abi_regex: catch the right exception for a bad regex
Date: Tue, 11 Aug 2026 10:40:44 -0600	[thread overview]
Message-ID: <87mruslier.fsf@trenco.lwn.net> (raw)
In-Reply-To: <9f6fa7a9aa6ba9a26b484b911976713356b3fd44.1786139549.git.alison.schofield@intel.com>

Alison Schofield <alison.schofield@intel.com> writes:

> While validating recent CXL ABI documentation updates with
> get_abi.py, the 'undefined' mode was found to abort instead of
> reporting undocumented ABI entries.
>
> Older Python releases raise re.error, while newer releases expose
> re.PatternError. Catching the compatible re.error exception handles
> both cases.
>
> Use re.error so the scan continues and reports the remaining
> results.
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> ---
>
> Changes in v2:
> - Update commit msg to say catches the compatible re.error (Sashiko)
> - No code change
>
>
>  tools/lib/python/abi/abi_regex.py | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

Applied, thanks.

jon

      parent reply	other threads:[~2026-08-11 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 22:10 [PATCH v2 1/2] docs: python: abi_regex: catch the right exception for a bad regex Alison Schofield
2026-08-07 22:10 ` [PATCH v2 2/2] docs: python: abi_regex: convert adjacent index placeholders Alison Schofield
2026-08-11 16:40   ` Jonathan Corbet
2026-08-11 16:40 ` 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=87mruslier.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=alison.schofield@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=skhan@linuxfoundation.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