From: Jakub Kicinski <kuba@kernel.org>
To: patchwork-bot+netdevbpf@kernel.org,
"helpdesk@kernel.org" <helpdesk@kernel.org>
Cc: Rahul Rameshbabu <rrameshbabu@nvidia.com>,
netdev@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: pw bot mismatches on pure rename patches (was: Re: [PATCH net-next 1/2] tools: ynl: Remove absolute paths to yaml files from ethtool testing tool)
Date: Thu, 13 Apr 2023 08:00:10 -0700 [thread overview]
Message-ID: <20230413080010.7e69dde3@kernel.org> (raw)
In-Reply-To: <168135961849.12762.11668973666026729971.git-patchwork-notify@kernel.org>
On Thu, 13 Apr 2023 04:20:18 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
> Here is the summary with links:
> - [net-next,1/2] tools: ynl: Remove absolute paths to yaml files from ethtool testing tool
> (no matching commit)
> - [net-next,2/2] tools: ynl: Rename ethtool to ethtool.py
> https://git.kernel.org/netdev/net-next/c/f2b3b6a22df7
>
> You are awesome, thank you!
Hi Konstantin,
this may be worth investigating, looks like a generic bug. The patch:
https://lore.kernel.org/all/20230413012252.184434-2-rrameshbabu@nvidia.com/
has no diff, so I'm guessing it confused the bot and the bot matched
on whatever got pushed into the tree next.
next prev parent reply other threads:[~2023-04-13 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 1:22 [PATCH net-next 1/2] tools: ynl: Remove absolute paths to yaml files from ethtool testing tool Rahul Rameshbabu
2023-04-13 1:22 ` [PATCH net-next 2/2] tools: ynl: Rename ethtool to ethtool.py Rahul Rameshbabu
2023-04-13 4:20 ` [PATCH net-next 1/2] tools: ynl: Remove absolute paths to yaml files from ethtool testing tool patchwork-bot+netdevbpf
2023-04-13 15:00 ` Jakub Kicinski [this message]
2023-04-14 5:20 ` patchwork-bot+netdevbpf
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=20230413080010.7e69dde3@kernel.org \
--to=kuba@kernel.org \
--cc=helpdesk@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=rrameshbabu@nvidia.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;
as well as URLs for NNTP newsgroup(s).