From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
sashiko@lists.linux.dev
Subject: Could we command Sashiko for "Failed to apply"? (was "Re: [RFC PATCH v2 0/7] Implement a new generic pagewalk API")
Date: Sun, 26 Apr 2026 13:47:45 -0700 [thread overview]
Message-ID: <20260426204746.93567-1-sj@kernel.org> (raw)
In-Reply-To: <20260426061148.944a69c2cb020b0d51f13f6a@linux-foundation.org>
+ sashiko@lists.linux.dev
- lists and people who might not interested in Sashiko discussion
On Sun, 26 Apr 2026 06:11:48 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sun, 26 Apr 2026 14:57:12 +0200 Oscar Salvador <osalvador@suse.de> wrote:
>
> > Also, I would like to thank Vlastimil, who helped me running this
> > patchset quite a few times through Claude, to catch some fixes.
>
> Well dang, I wanted to do a Claude-vs-Sashiko cage match, but "Failed
> to apply". Again :(
> (https://sashiko.dev/#/patchset/20260426125719.24698-1-osalvador@suse.de).
I also got [1] a "Failed to apply" yesterday. For that, I was asking a way to
make this better for only DAMON patches. But seems DAMON is not a single user
who getting this problem.
I'm wondering if we could have some kind of magic words for Sashiko, like the
syzbot has. That is, replying to a patch with a magic words and the baseline
info like below makes Sashiko tries applying patches again with the given
baseline.
E.g., #sashiko-retry-baseline git://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git 0123456789ab
Never an urgent request, but just a brainstorming attempt.
[1] https://lore.kernel.org/20260425221630.81644-1-sj@kernel.org
Thanks,
SJ
[...]
parent reply other threads:[~2026-04-26 20:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260426061148.944a69c2cb020b0d51f13f6a@linux-foundation.org>]
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=20260426204746.93567-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.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