Linux Perf Users
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Michael Petlan <mpetlan@redhat.com>
Cc: 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: Mon, 5 Oct 2026 15:47:25 -0700	[thread overview]
Message-ID: <asQo_ZqrjOAoJ1ux@google.com> (raw)
In-Reply-To: <20260924223027.799654-1-mpetlan@redhat.com>

Hello,

On Fri, Sep 25, 2026 at 12:30:25AM +0200, Michael Petlan wrote:
> Hello all,
> 
> 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
> 
> 
> 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

Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks,
Namhyung


  parent reply	other threads:[~2026-10-05 22:47 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 ` Namhyung Kim [this message]
2026-10-06 13:13   ` [PATCH 0/2] perf test attr: Fix and re-enable the test Arnaldo Carvalho de Melo

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=asQo_ZqrjOAoJ1ux@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@redhat.com \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mpetlan@redhat.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