From: Jakub Kicinski <kuba@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
helpdesk@kernel.org, davem@davemloft.net,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [GIT PULL] bluetooth 2026-03-12
Date: Wed, 18 Mar 2026 19:48:22 -0700 [thread overview]
Message-ID: <20260318194822.434c0485@kernel.org> (raw)
In-Reply-To: <20260315132013.75ab40c5@kernel.org>
On Sun, 15 Mar 2026 13:20:13 -0700 Jakub Kicinski wrote:
> On Sun, 15 Mar 2026 11:04:47 -0400 Konstantin Ryabitsev wrote:
> > On Sat, Mar 14, 2026 at 10:44:36AM -0700, Jakub Kicinski wrote:
> > > To be clear I have pulled already, if any of the AI reports looks
> > > urgent please send a follow up.
> > >
> > > Hello helpdesk! The patchwork reply bot has not been replying to pull
> > > requests for us in the last few weeks. Is this an intentional change?
> >
> > It was an intentional change to make it work more reliably, but we clearly
> > failed because it stopped matching altogether. *sigh*
> >
> > I think I found where the match was failing and added tests to check for it.
> > It won't work retroactively, but it should find future pull requests
> > (hopefully!)
>
> Thank you! I'll report back in a couple of days.
Since I promised - pw-bot replies to pulls seem to be working fine now
next prev parent reply other threads:[~2026-03-19 2:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:06 [GIT PULL] bluetooth 2026-03-12 Luiz Augusto von Dentz
2026-03-14 16:47 ` Jakub Kicinski
2026-03-16 13:58 ` Luiz Augusto von Dentz
2026-03-16 23:26 ` Jakub Kicinski
2026-03-17 20:45 ` Luiz Augusto von Dentz
2026-03-14 17:44 ` Jakub Kicinski
2026-03-15 15:04 ` Konstantin Ryabitsev
2026-03-15 20:20 ` Jakub Kicinski
2026-03-19 2:48 ` Jakub Kicinski [this message]
2026-03-19 13:21 ` Konstantin Ryabitsev
2026-04-10 16:06 ` patchwork-bot+bluetooth
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=20260318194822.434c0485@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=helpdesk@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=mricon@kernel.org \
--cc=netdev@vger.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.