From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
John Garry <john.g.garry@oracle.com>,
Sandipan Das <sandipan.das@amd.com>, Xu Yang <xu.yang_2@nxp.com>,
Benjamin Gray <bgray@linux.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf jevents: Fix build issue in '*/' in event descriptions
Date: Tue, 10 Dec 2024 17:01:21 -0300 [thread overview]
Message-ID: <Z1ieEX22EyS-v36o@x1> (raw)
In-Reply-To: <Z1idV3K4RxLdMhT_@x1>
On Tue, Dec 10, 2024 at 04:58:19PM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Dec 10, 2024 at 11:24:28AM -0800, Ian Rogers wrote:
> > On Tue, Dec 10, 2024 at 11:17 AM Arnaldo Carvalho de Melo
> > > On Tue, Dec 10, 2024 at 10:15:30AM -0300, Arnaldo Carvalho de Melo wrote:
> > > > Probably best to have big patches via perf-tools-next at this point in
> > > > time.
> > >
> > > I'm seeing this after applying:
> > >
> > > /home/acme/git/perf-tools-next/tools/perf/pmu-events/jevents.py:434: SyntaxWarning: invalid escape sequence '\*'
> > > return s.replace('*/', '\*\/')
> >
> > It likely needs to be:
> > ```
> > return s.replace('*/', r'\*\/')
> > ```
> > note the r. Could you test for me?
>
> Sure.
Yeah, no more warning, thanks, fixed it up.
- Arnaldo
next prev parent reply other threads:[~2024-12-10 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 16:55 [PATCH v1] perf jevents: Fix build issue in '*/' in event descriptions Ian Rogers
2024-12-09 18:35 ` Ian Rogers
2024-12-09 20:28 ` Arnaldo Carvalho de Melo
2024-12-09 21:29 ` Ian Rogers
2024-12-10 13:15 ` Arnaldo Carvalho de Melo
2024-12-10 19:17 ` Arnaldo Carvalho de Melo
2024-12-10 19:24 ` Ian Rogers
2024-12-10 19:58 ` Arnaldo Carvalho de Melo
2024-12-10 20:01 ` Arnaldo Carvalho de Melo [this message]
2024-12-10 20:21 ` Ian Rogers
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=Z1ieEX22EyS-v36o@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgray@linux.ibm.com \
--cc=irogers@google.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=xu.yang_2@nxp.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 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.