From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Alan Maguire <alan.maguire@oracle.com>,
sashiko@lists.linux.dev, dwarves@vger.kernel.org
Subject: Re: Sashiko reviews for pahole: missing custom_remotes
Date: Mon, 22 Jun 2026 17:30:30 -0300 [thread overview]
Message-ID: <ajmbZlAU17yPbOft@x1> (raw)
In-Reply-To: <ajmYLrz2qbUoRx8k@x1>
On Mon, Jun 22, 2026 at 05:16:46PM -0300, Arnaldo Carvalho de Melo wrote:
> On Mon, Jun 22, 2026 at 12:18:10PM -0700, Roman Gushchin wrote:
> > Sashiko is not really officially supporting a non-kernel code yet. It might work occasionally,
> > but I can’t guarantee anything and results might be pathetic.
> I'm using it locally with great results, using:
> acme@number:~/git/sashiko$ cat Settings.toml | grep -B1 -A3 'dwarves\|pahole'
> [mailing_lists]
> track = ["linux-kernel", "dwarves"]
> [nntp]
> server = "nntp.lore.kernel.org"
> --
> [[git.custom_remotes]]
> name = "pahole"
> url = "git://git.kernel.org/pub/scm/devel/pahole/pahole.git"
> check_all_branches = false
> only_branches = ["next", "master"]
> acme@number:~/git/sashiko$
> Submitting series to sashiko with:
> $ sashiko-cli submit FIRST_SHA^..LAST_SHA --repo /home/acme/git/pahole
> With great results, for instance:
> > We might explore adding support for more project going forward, but we’re not there yet.
> Your call, but just as a data point, its being useful for me for pahole
> development and I bet other pahole developers would like having it
> enabled, since it seems to be useful with the current sashiko codebase.
This series:
https://lore.kernel.org/all/20260622202441.14799-1-acme@kernel.org/
For instance, has several bugs addressed from review comments by
Sashiko, that is credited:
commit bf5e28c65bc52e61361a676acc9d2913b6d9e065
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Fri Jun 19 11:34:02 2026 -0300
tests: Guard cleanup() against empty outdir to prevent rm /*
If make_tmpdir() fails, outdir is empty. The cleanup() function
executes rm ${outdir}/* which expands to rm /* when outdir is unset or
empty — potentially deleting the entire root filesystem.
Add a guard to check that outdir is non-empty and points to an existing
directory before attempting removal.
Fixes: 52dbfb0b39595ed8 ("pahole: Refactor selftests")
Reported-by: Sashiko:gemini-3-1-pro-preview # Running on a local machine
Assisted-by: Claude:claude-opus-4-6
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cheers,
- Arnald
prev parent reply other threads:[~2026-06-22 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 19:30 Sashiko reviews for pahole: missing custom_remotes Arnaldo Carvalho de Melo
2026-06-22 19:18 ` Roman Gushchin
2026-06-22 20:16 ` Arnaldo Carvalho de Melo
2026-06-22 20:30 ` 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=ajmbZlAU17yPbOft@x1 \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=dwarves@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=sashiko@lists.linux.dev \
/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