From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Michael Petlan <mpetlan@redhat.com>,
linux-perf-users@vger.kernel.org, irogers@google.com,
acme@redhat.com
Subject: Re: [PATCH 0/2] perf test attr: Fix and re-enable the test
Date: Tue, 6 Oct 2026 15:13:36 +0200 [thread overview]
Message-ID: <asT0AIC8cAYy0AKD@x2> (raw)
In-Reply-To: <asQo_ZqrjOAoJ1ux@google.com>
On Mon, Oct 05, 2026 at 03:47:25PM -0700, Namhyung Kim wrote:
> On Fri, Sep 25, 2026 at 12:30:25AM +0200, Michael Petlan wrote:
> > I have noticed that a testcase formerly known as "Setup struct perf_event_attr",
> > later renamed to "Perf attribute expectations test" has been disabled by
> > accident during the move.
> > That also probably led to forgetting to update the struct size, which is now
> > fixed by the second patch.
> > Michael Petlan (2):
> > perf test attr: Propagate the return value from the test to the
> > wrapper
> > perf test attr: Fix wrong size expectation for events
> The "Fixes" tag format is a bit different, but otherwise
I fixed the Fixes tags.
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, applied both patches,
- Arnaldo
prev parent reply other threads:[~2026-10-06 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 22:30 [PATCH 0/2] perf test attr: Fix and re-enable the test Michael Petlan
2026-09-24 22:30 ` [PATCH 1/2] perf test attr: Propagate the return value from the test to the wrapper Michael Petlan
2026-09-24 22:32 ` sashiko-bot
2026-09-24 22:30 ` [PATCH 2/2] perf test attr: Fix wrong size expectation for events Michael Petlan
2026-09-24 22:34 ` sashiko-bot
2026-10-06 13:33 ` Arnaldo Carvalho de Melo
2026-10-06 15:26 ` Arnaldo Carvalho de Melo
2026-10-05 22:47 ` [PATCH 0/2] perf test attr: Fix and re-enable the test Namhyung Kim
2026-10-06 13:13 ` Arnaldo Carvalho de Melo [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=asT0AIC8cAYy0AKD@x2 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.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