From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-bluetooth@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: bluetooth regression fix likely to miss -rc5 (was: Re: [GIT PULL] bluetooth 2026-03-19)
Date: Fri, 20 Mar 2026 17:52:20 -0700 [thread overview]
Message-ID: <20260320175220.47147285@kernel.org> (raw)
In-Reply-To: <CABBYNZJfLf6PzKUkGjiCvqEm3h0+3SUcxY5RNbUHv6LBdPT_zQ@mail.gmail.com>
On Fri, 20 Mar 2026 14:02:34 -0400 Luiz Augusto von Dentz wrote:
> Afaik, it was tagged as regression on March 1st afaik, according to
> [2]; traces were only provided on March 15th, so yeah it was fixed
> within a week once the necessary traces were supplied.
Hi Luiz, I don't really care about the complaint, just wanted to check
whether you know that we always send the PR on Thu (either AM or PM
depending on which maintainer is handling it)? If you do then nothing
to see here, we are all doing our best. But if it's not crystal clear
I should probably ping all sub-trees to remind folks.
next prev parent reply other threads:[~2026-03-21 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 19:04 [GIT PULL] bluetooth 2026-03-19 Luiz Augusto von Dentz
2026-03-20 0:00 ` patchwork-bot+netdevbpf
2026-03-20 16:47 ` bluetooth regression fix likely to miss -rc5 (was: Re: [GIT PULL] bluetooth 2026-03-19) Thorsten Leemhuis
2026-03-20 18:02 ` Luiz Augusto von Dentz
2026-03-20 18:26 ` bluetooth regression fix likely to miss -rc5 Thorsten Leemhuis
2026-03-20 21:03 ` bluetooth regression fix likely to miss -rc5 (was: Re: [GIT PULL] bluetooth 2026-03-19) Linus Torvalds
2026-03-20 21:19 ` Linus Torvalds
2026-03-21 18:50 ` Luiz Augusto von Dentz
2026-03-21 20:09 ` Linus Torvalds
2026-03-21 0:52 ` Jakub Kicinski [this message]
2026-03-21 18:36 ` Luiz Augusto von Dentz
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=20260320175220.47147285@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@leemhuis.info \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox