From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Chris Mason <clm@meta.com>
Subject: Re: Perf review prompts
Date: Fri, 15 May 2026 22:09:05 -0300 [thread overview]
Message-ID: <agfDsTgSyTRNIwgA@x1> (raw)
In-Reply-To: <CAP-5=fW5Wozj=F2dnXoLTWmUjudNWLyjjg95CuP3Jk9bLcYwww@mail.gmail.com>
On Fri, May 15, 2026 at 04:52:43PM -0700, Ian Rogers wrote:
> I think we can improve the review prompts for Sashiko and others, so I
> sent out this PR:
> https://github.com/masoncl/review-prompts/pull/62
> I wanted to advertise this and suggest that others contribute similarly.
Thanks for working on this, from a quick look it seems sane, some
comments:
-----
The "File Descriptor and Directory Stream Management" is describing
the dir equivalent of open and close and saying they need to be
paired. Assume this is base knowledge for an AI code review tool.
-----
That is completely reasonable expectation, I would be surprised if it
wouldn't catch this, but have you tested it?
For the validation of perf.data headers I plan to contribute what I
learned while working on:
[PATCH 00/28] perf: Harden perf.data parsing against crafted/corrupted files
https://lore.kernel.org/all/20260510033424.255812-1-acme@kernel.org>
That I hope soon to satisfy the last review comments from sashiko
addressed.
Anyway, I think this can be added FWIW:
Reviewed-by: Arnaldo Carvalho de Melo <acme@redhat.com>
- Arnaldo
prev parent reply other threads:[~2026-05-16 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 23:52 Perf review prompts Ian Rogers
2026-05-16 1:09 ` 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=agfDsTgSyTRNIwgA@x1 \
--to=acme@kernel.org \
--cc=clm@meta.com \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--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 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.