From: Jakub Kicinski <kuba@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@kernel.org
Subject: Re: patchwork-bot incorrect reports
Date: Mon, 12 May 2025 10:31:55 -0700 [thread overview]
Message-ID: <20250512103155.76f3b6c2@kernel.org> (raw)
In-Reply-To: <CAMuHMdWgwiNcHHopCCMLcidDkunhbGD+ZpMSoOAXy=PvoTVzYA@mail.gmail.com>
On Mon, 12 May 2025 15:27:57 +0200 Geert Uytterhoeven wrote:
> Hi Konstantin,
>
> For quite a while, sometimes the patchwork-bot incorrectly reports that
> a patch was applied. Usually this happens when a series is applied
> partially. In that case, sometimes one or more of the unapplied
> patches still appear in the patchwork-bot email report, while they are
> still marked as "Action Required" in patchwork, so no real harm is done.
>
> However, today I got a report[1] that is worse:
> 1. It claims that Jakub Kicinski applied a patch to my repository,
> 2. Its patchwork state[2] was changed to "Mainlined",
> 3. Its patchwork entry points to an unrelated merge commit in netdev[3].
>
> Do you know what's going on?
> Thanks!
>
> [1] https://lore.kernel.org/all/174703868703.506001.16395245401308177497.git-patchwork-summary@kernel.org
> [2] https://patchwork.kernel.org/project/linux-renesas-soc/patch/TYRPR01MB14284C8E8145635A1AD8314F4828AA@TYRPR01MB14284.jpnprd01.prod.outlook.com
> [3] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ccb52a9c8dfaa4e2cbb2524b68a7ead72038b039
Hm, weird. I wonder if I'm doing something special. BPF had a similar
problem and it's usually my merge commits.
Maybe it's because I add https://patch.msgid.link URLs to merge commits,
which are technically not patches? Should I switch to lore links on
merges but stick to patch.msgid.link on patches?
next prev parent reply other threads:[~2025-05-12 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:27 patchwork-bot incorrect reports Geert Uytterhoeven
2025-05-12 17:31 ` Jakub Kicinski [this message]
2025-05-15 13:56 ` Konstantin Ryabitsev
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=20250512103155.76f3b6c2@kernel.org \
--to=kuba@kernel.org \
--cc=geert@linux-m68k.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@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.