From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCHES v8 0/2] perf c2c hardening
Date: Fri, 7 Aug 2026 08:58:28 -0300 [thread overview]
Message-ID: <anXIZPk2CKikT30v@x1> (raw)
In-Reply-To: <CAP-5=fXj1xp+7vwnhGzPnLwxm8jT3WSkJe972fF2Rq9CM5ioxQ@mail.gmail.com>
On Wed, Aug 05, 2026 at 04:58:37PM -0700, Ian Rogers wrote:
> On Wed, Aug 5, 2026 at 9:33 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > On Wed, Aug 05, 2026 at 12:10:41PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Please consider merging,
> > > Two hardening fixes for perf c2c found by the sashiko-bot AI reviewer.
> > This short series is finally completely Sashiko clean:
> > https://sashiko.dev/#/patchset/20260805151043.237233-1-acme%40kernel.org
> With:
> https://github.com/sashiko-dev/sashiko/pull/363
> I thought we'd start getting positive emails. Perhaps we're waiting
> for the server to rebuild or reboot.
Roman is on PTO, there is a pile of requests that is getting mountain
sized 8-)
- Arnaldo
next prev parent reply other threads:[~2026-08-07 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 15:10 [PATCHES v8 0/2] perf c2c hardening Arnaldo Carvalho de Melo
2026-08-05 15:10 ` [PATCH 1/2] perf c2c: Fix error masking, OOM, and unchecked caller errors in hpp_list__parse() Arnaldo Carvalho de Melo
2026-08-06 0:00 ` Ian Rogers
2026-08-05 15:10 ` [PATCH 2/2] perf c2c: Clean up registered formats on c2c_hists__init() and c2c_hists__reinit() failure Arnaldo Carvalho de Melo
2026-08-06 0:02 ` Ian Rogers
2026-08-05 16:33 ` [PATCHES v8 0/2] perf c2c hardening Arnaldo Carvalho de Melo
2026-08-05 23:58 ` Ian Rogers
2026-08-07 11:58 ` Arnaldo Carvalho de Melo [this message]
2026-08-06 16:17 ` Namhyung Kim
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=anXIZPk2CKikT30v@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@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