All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	Johan Hovold <johan+linaro@kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org,
	Janaki Ramaiah Thota <quic_janathot@quicinc.com>
Subject: Re: [PATCH] Revert "Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT"
Date: Tue, 26 Mar 2024 17:20:34 +0100	[thread overview]
Message-ID: <ZgL10ur0825LgWVK@hovoldconsulting.com> (raw)
In-Reply-To: <ZgLnOHiCzo5AQzra@hovoldconsulting.com>

Hi Luiz,

On Tue, Mar 26, 2024 at 04:18:16PM +0100, Johan Hovold wrote:
> On Tue, Mar 26, 2024 at 10:17:13AM -0400, Luiz Augusto von Dentz wrote:
> > On Tue, Mar 26, 2024 at 3:09 AM Johan Hovold <johan@kernel.org> wrote:
> > > On Mon, Mar 25, 2024 at 04:31:53PM -0400, Luiz Augusto von Dentz wrote:

> > > > All the
> > > > CI automation is done on bluetooth-next and if you are asking to be
> > > > done via bluetooth tree which is based on the latest rc that is not
> > > > how things works here, we usually first apply to bluetooth-next and in
> > > > case it needs to be backported then it later done via pull-request.
> > >
> > > The revert fixes a regression in 6.7-rc7 and should get to Linus as soon
> > > as possible and I assume you have some way to get fixes into mainline
> > > for the current development cycle.
> > 
> > Yeah I will send it later today to be included in the next rc release
> > and since it is marked for stable that shall trigger the process of
> > backporting it.
> > 
> > > The series fixes a critical bug in the Qualcomm driver and should
> > > similarly get into mainline as soon as possible to avoid having people
> > > unknowingly start relying on the broken behaviour (reversed address).
> > > The bug in this case is older, but since the bug is severe and we're
> > > only at rc1, I don't think this one should wait for 6.10 either.

I just double checked the bluetooth-next branch and everything looks
good now (revert + endianness fix series). Thanks!

Did I understand you correctly that you'll be able to get all five
commits into 6.9 during this development cycle (e.g. 6.9-rc2)?
 
Johan

  reply	other threads:[~2024-03-26 16:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  8:44 [PATCH] Revert "Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT" Johan Hovold
2024-03-14  9:32 ` bluez.test.bot
2024-03-14 14:30 ` [PATCH] " Luiz Augusto von Dentz
2024-03-14 15:07   ` Johan Hovold
2024-03-25 13:57     ` Linux regression tracking (Thorsten Leemhuis)
2024-03-25 17:10       ` Luiz Augusto von Dentz
2024-03-25 17:24         ` Johan Hovold
2024-03-25 19:39           ` Luiz Augusto von Dentz
2024-03-25 19:48             ` Johan Hovold
2024-03-25 20:07               ` Luiz Augusto von Dentz
2024-03-25 20:14                 ` Johan Hovold
2024-03-25 20:31                   ` Luiz Augusto von Dentz
2024-03-26  7:09                     ` Johan Hovold
2024-03-26 14:17                       ` Luiz Augusto von Dentz
2024-03-26 15:18                         ` Johan Hovold
2024-03-26 16:20                           ` Johan Hovold [this message]
2024-03-26 16:58                             ` Luiz Augusto von Dentz
2024-03-26 17:08                               ` Johan Hovold
2024-03-14 17:01 ` Clayton Craft
2024-03-26 15:30 ` patchwork-bot+bluetooth
2024-03-28 14:55   ` Janaki Ramaiah Thota
2024-03-28 15:23     ` Johan Hovold
2024-03-29  7:25       ` Janaki Ramaiah Thota
2024-04-03 12:24         ` Johan Hovold
2024-04-05 12:59           ` Janaki Ramaiah Thota
2024-04-15 10:52             ` Janaki Ramaiah Thota
2024-04-15 11:20               ` Johan Hovold
2024-04-16  9:20                 ` Johan Hovold

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=ZgL10ur0825LgWVK@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=quic_janathot@quicinc.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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.