From: Tengfei Fan <quic_tengfan@quicinc.com>
To: Trilok Soni <quic_tsoni@quicinc.com>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>
Cc: <keescook@chromium.org>, <tony.luck@intel.com>,
<gpiccoli@igalia.com>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-hardening@vger.kernel.org>, <kernel@quicinc.com>
Subject: Re: [PATCH v6 RESEND 0/4] arm64: qcom: add AIM300 AIoT board support
Date: Tue, 2 Apr 2024 10:29:06 +0800 [thread overview]
Message-ID: <2d35eb0c-2a89-4e06-bb29-b4a9fc531446@quicinc.com> (raw)
In-Reply-To: <31f0b5d2-5b92-cc74-68bd-94fd42527a22@quicinc.com>
On 4/1/2024 11:54 PM, Trilok Soni wrote:
> On 4/1/2024 2:38 AM, Tengfei Fan wrote:
>> Here is a diagram of AIM300 AIoT Carrie Board and SoM
>> +--------------------------------------------------+
>> | AIM300 AIOT Carrie Board |
>
> spellcheck
>
> s/Carrie/Carrier ?
Thanks Trilok for pointing out the problem here, I will correct this
typo in next version patch series.
>
--
Thx and BRs,
Tengfei Fan
prev parent reply other threads:[~2024-04-02 2:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 9:38 [PATCH v6 RESEND 0/4] arm64: qcom: add AIM300 AIoT board support Tengfei Fan
2024-04-01 9:38 ` [PATCH v6 RESEND 1/4] dt-bindings: arm: qcom: Document QCS8550 SoC and the AIM300 AIoT board Tengfei Fan
2024-04-01 9:38 ` [PATCH v6 RESEND 2/4] arm64: dts: qcom: qcs8550: introduce qcs8550 dtsi Tengfei Fan
2024-04-01 19:13 ` Dmitry Baryshkov
2024-04-01 9:38 ` [PATCH v6 RESEND 3/4] arm64: dts: qcom: add base AIM300 dtsi Tengfei Fan
2024-04-01 9:38 ` [PATCH v6 RESEND 4/4] arm64: dts: qcom: aim300: add AIM300 AIoT Tengfei Fan
2024-04-01 19:22 ` Dmitry Baryshkov
2024-04-02 2:26 ` Tengfei Fan
2024-04-01 15:54 ` [PATCH v6 RESEND 0/4] arm64: qcom: add AIM300 AIoT board support Trilok Soni
2024-04-02 2:29 ` Tengfei Fan [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=2d35eb0c-2a89-4e06-bb29-b4a9fc531446@quicinc.com \
--to=quic_tengfan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tsoni@quicinc.com \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).