From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3E73B13CA98; Tue, 26 Mar 2024 16:20:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711470027; cv=none; b=Fw4GL4TrfuRDdq7Gpqb6IDhhkJ4Mr6nXSTj5g5tjPHpKviFSvVwNqdAXVa7qbDwdMqt7ZXcQu+zeNFL2g8mbismeGw0d38j/6BDO1lOdCvD+1okBB/7ZccwyTkHUuh4XdfNqHtPSGGzgcg2RhwXMDGjmlsG1KVRcP+rlTaO63wA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711470027; c=relaxed/simple; bh=tH7ShG5e19q5dk8DGs/7rFZaClfulgISrGFPuWcP0mg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=CWAkjnaQ1RMfxJ58iRTpgBFDJVYthH8VLGqhuMzy8ShmMWfbB0sREts2gNmmNku0lYma4XhaWgAmoud6U135rXq1jjTPvZhHJn1Vneiqj5Rz+tl3i3Rtc+C0/CYv9aaa3IRjD07a2R0IF3vhoe9mEfnitb08LSet+FGkD++e8lY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=e6C92dz6; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="e6C92dz6" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C3EE8C43394; Tue, 26 Mar 2024 16:20:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1711470026; bh=tH7ShG5e19q5dk8DGs/7rFZaClfulgISrGFPuWcP0mg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=e6C92dz6raZp0WrjtLHCxqpCcVWV3awH3jwOkT/LShocw+towYCYzHIpMxVqVR6ci S4vUVgmYGNay0dotswGf42xd6YmI7FN3UtHnq6i4yoeLo+CYBvI39oh+zvkPu/nwP6 ze88G0lKQJKrmGrEVoi348mOb39+eZjNn3WGMk9Elebb301GZ8pneFWt9kNFD/0BoR C2ADW6obNGlsFyXcw3F6Z0qvBucbUllRtd/Dd06q/8Xx85VfeplO6YXdN3Kd3Ia0RI O4dyir2E/RrcwhToChH4LNMoUI3HwPM4CWyWULbzkCZysMCLqQdXDQiswmdtYCXJOZ munyLNIT7r7zQ== Received: from johan by xi.lan with local (Exim 4.97.1) (envelope-from ) id 1rp9XO-000000006Yi-1ZUs; Tue, 26 Mar 2024 17:20:35 +0100 Date: Tue, 26 Mar 2024 17:20:34 +0100 From: Johan Hovold To: Luiz Augusto von Dentz Cc: Linux regressions mailing list , Johan Hovold , Marcel Holtmann , linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Janaki Ramaiah Thota Subject: Re: [PATCH] Revert "Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT" Message-ID: References: Precedence: bulk X-Mailing-List: linux-bluetooth@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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 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