From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Praveen Talari <praveen.talari@oss.qualcomm.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, bryan.odonoghue@linaro.org,
dmitry.baryshkov@oss.qualcomm.com, andersson@kernel.org,
psodagud@quicinc.com, djaggi@quicinc.com,
quic_msavaliy@quicinc.com, quic_vtanuku@quicinc.com,
quic_arandive@quicinc.com, quic_shazhuss@quicinc.com,
quic_cchiluve@quicinc.com
Subject: Re: [PATCH v1] serial: qcom_geni: Fix BT failure regression on RB2 platform
Date: Wed, 7 Jan 2026 08:25:22 +0100 [thread overview]
Message-ID: <2026010708-bucked-backstage-fd78@gregkh> (raw)
In-Reply-To: <20260107064834.1006428-1-praveen.talari@oss.qualcomm.com>
On Wed, Jan 07, 2026 at 12:18:34PM +0530, Praveen Talari wrote:
> A regression in linux-next causes Bluetooth functionality to fail during
> bootup on the RB2 platform, preventing proper BT initialization. However,
> BT works correctly after bootup completes.
You mean "6.19-rc1", not "linux-next" here.
prev parent reply other threads:[~2026-01-07 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 6:48 [PATCH v1] serial: qcom_geni: Fix BT failure regression on RB2 platform Praveen Talari
2026-01-07 6:54 ` Dmitry Baryshkov
2026-01-07 7:06 ` Praveen Talari
2026-01-07 7:22 ` Dmitry Baryshkov
2026-01-07 9:24 ` Praveen Talari
2026-01-07 10:46 ` Konrad Dybcio
2026-01-07 10:58 ` Praveen Talari
2026-01-07 11:35 ` Dmitry Baryshkov
2026-01-07 14:08 ` Praveen Talari
2026-01-07 16:13 ` Dmitry Baryshkov
2026-01-07 7:25 ` Greg Kroah-Hartman
2026-01-07 7:25 ` Greg Kroah-Hartman [this message]
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=2026010708-bucked-backstage-fd78@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=djaggi@quicinc.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jirislaby@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=praveen.talari@oss.qualcomm.com \
--cc=psodagud@quicinc.com \
--cc=quic_arandive@quicinc.com \
--cc=quic_cchiluve@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_shazhuss@quicinc.com \
--cc=quic_vtanuku@quicinc.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