From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexander Martinz <amartinz@shiftphones.com>,
~postmarketos/upstreaming@lists.sr.ht
Cc: phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dylan Van Assche <me@dylanvanassche.be>
Subject: Re: [PATCH 1/2] arch: arm64: qcom: sdm845-shift-axolotl: fix Bluetooth firmware loading
Date: Thu, 9 Jun 2022 14:11:59 +0200 [thread overview]
Message-ID: <fd3ae279-eb0e-ec5b-2611-15ada34a9c66@linaro.org> (raw)
In-Reply-To: <20220609095412.211060-1-amartinz@shiftphones.com>
On 09/06/2022 11:54, Alexander Martinz wrote:
> From: Dylan Van Assche <me@dylanvanassche.be>
>
> Add hsuart0 alias, firmware name and prevent garbage data on Bluetooth UART lines
> on the SHIFT 6mq based on the Qualcomm SDM845 chip.
> I discovered that these were missing by comparing the DTS with similar
> devices such as the Oneplus 6/6T and Dragonboard 845c.
>
> Signed-of-by: Dylan Van Assche <me@dylanvanassche.be>
> Tested-by: Alexander Martinz <amartinz@shiftphones.co>
Thanks for the patch. Instead of your Tested-by (or beside) your SoB is
needed, following Dylan's.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-09 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 9:54 [PATCH 1/2] arch: arm64: qcom: sdm845-shift-axolotl: fix Bluetooth firmware loading Alexander Martinz
2022-06-09 9:54 ` [PATCH 2/2] arm64: dts: qcom/sdm845-shift-axolotl: Add audio support Alexander Martinz
2022-06-09 12:14 ` Krzysztof Kozlowski
2022-06-09 17:07 ` Stephan Gerhold
2022-06-09 17:19 ` Luca Weiss
2022-06-09 12:11 ` Krzysztof Kozlowski [this message]
2022-06-09 12:47 ` [PATCH 1/2] arch: arm64: qcom: sdm845-shift-axolotl: fix Bluetooth firmware loading Dmitry Baryshkov
2022-07-06 18:49 ` Caleb Connolly
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=fd3ae279-eb0e-ec5b-2611-15ada34a9c66@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=amartinz@shiftphones.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@dylanvanassche.be \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).