From: Oliver Sang <oliver.sang@intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
<oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
James Clark <james.clark@linaro.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@arm.com>,
Atish Patra <atishp@atishpatra.org>,
Mingwei Zhang <mizhang@google.com>,
Kajol Jain <kjain@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
<linux-perf-users@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [linus:master] [perf tools] af954f76ee: perf-sanity-tests.Test_data_symbol.fail
Date: Thu, 12 Dec 2024 10:00:39 +0800 [thread overview]
Message-ID: <Z1pDx0TFKsYZvGCl@xsang-OptiPlex-9020> (raw)
In-Reply-To: <Z1nLcMDTFAFuX809@google.com>
hi, Namhyung,
On Wed, Dec 11, 2024 at 09:27:12AM -0800, Namhyung Kim wrote:
[...]
> > It should have that precise level reflected in the evsel name :-\
> >
> > Ran out of time, hope the above helps.
> >
> > Apart from that, from a purely regression fix, your patch gets the
> > previous behaviour, from this isolated test I made, so:
> >
> > Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Applied to perf-tools, thanks!
sorry for late. just FYI.
we finally finished the test with your patch, and confirmed
perf-sanity-tests.Test_data_symbol can pass now.
Tested-by: kernel test robot <oliver.sang@intel.com>
>
> Best regards,
> Namhyung
>
>
next prev parent reply other threads:[~2024-12-12 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 7:03 kernel test robot
2024-12-02 20:32 ` Namhyung Kim
2024-12-04 14:04 ` Oliver Sang
2024-12-04 21:44 ` Namhyung Kim
2024-12-04 22:21 ` Namhyung Kim
2024-12-05 15:30 ` Arnaldo Carvalho de Melo
2024-12-11 17:27 ` Namhyung Kim
2024-12-12 2:00 ` Oliver Sang [this message]
2024-12-06 2:10 ` Oliver Sang
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=Z1pDx0TFKsYZvGCl@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=acme@kernel.org \
--cc=atishp@atishpatra.org \
--cc=james.clark@arm.com \
--cc=james.clark@linaro.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mizhang@google.com \
--cc=namhyung@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=palmer@rivosinc.com \
--cc=ravi.bangoria@amd.com \
--cc=tmricht@linux.ibm.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
all inboxes | Powered by JetHome®