From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Vishal Chourasia <vishalc@linux.ibm.com>
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, haoluo@google.com,
hawk@kernel.org, john.fastabend@gmail.com, jolsa@kernel.org,
kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
netdev@vger.kernel.org, sachinp@linux.ibm.com, sdf@google.com,
song@kernel.org, yhs@fb.com
Subject: Re: [PATCH] Fix invalid escape sequence warnings
Date: Wed, 23 Aug 2023 14:14:48 +0530 [thread overview]
Message-ID: <20230823084448.GB1766638@linux.vnet.ibm.com> (raw)
In-Reply-To: <20230816122133.1231599-1-vishalc@linux.ibm.com>
* Vishal Chourasia <vishalc@linux.ibm.com> [2023-08-16 17:51:33]:
> The Python script `bpf_doc.py` uses regular expressions with
> backslashes in string literals, which results in SyntaxWarnings
> during its execution.
>
> This patch addresses these warnings by converting relevant string
> literals to raw strings, which interpret backslashes as literal
> characters. This ensures that the regular expressions are parsed
> correctly without causing any warnings.
>
> Signed-off-by: Vishal Chourasia <vishalc@linux.ibm.com>
> Reported-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Thanks, Works for me
Tested-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
--
Thanks and Regards
Srikar Dronamraju
prev parent reply other threads:[~2023-08-23 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 8:47 Warning when compiling with python3.12 Srikar Dronamraju
2023-08-16 12:21 ` [PATCH] Fix invalid escape sequence warnings Vishal Chourasia
2023-08-22 23:30 ` Andrii Nakryiko
2023-08-29 7:43 ` Vishal Chourasia
2023-08-29 7:49 ` [PATCH v2] " Vishal Chourasia
2023-08-30 15:21 ` Quentin Monnet
2023-08-31 12:00 ` patchwork-bot+netdevbpf
2023-08-23 8:44 ` Srikar Dronamraju [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=20230823084448.GB1766638@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sachinp@linux.ibm.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=vishalc@linux.ibm.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).