Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Slark Xiao" <slark_xiao@163.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>
Cc: manivannan.sadhasivam@linaro.org, loic.poulain@linaro.org,
	 ryazanov.s.a@gmail.com, johannes@sipsolutions.net,
	 quic_jhugo@quicinc.com, netdev@vger.kernel.org,
	mhi@lists.linux.dev,  linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v3 1/3] bus: mhi: host: Add Foxconn SDX72 related support
Date: Fri, 28 Jun 2024 16:31:40 +0800 (CST)	[thread overview]
Message-ID: <455cd5ee.86ad.1905df8bbab.Coremail.slark_xiao@163.com> (raw)
In-Reply-To: <2xbnsvtzh23al43njugtqpihocyo5gtyuzu4wbd5gmizhs2utf@d2x2gxust3w5>


At 2024-06-28 15:51:54, "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org> wrote:
>On Fri, Jun 28, 2024 at 03:36:05PM GMT, Slark Xiao wrote:
>> Align with Qcom SDX72, add ready timeout item for Foxconn SDX72.
>> And also, add firehose support since SDX72.
>> 
>> Signed-off-by: Slark Xiao <slark_xiao@163.com>
>> ---
>> v2: (1). Update the edl file path and name (2). Set SDX72 support
>> trigger edl mode by default
>> v3: Divide into 2 parts for Foxconn sdx72 platform
>
>Generic comment: please send all the patches using a single
>git-send-email command. This way it will thread them properly, so that
>they form a single patchseries in developers's mail clients. Or you can
>just use 'b4' tool to manage and send the patchset.
>

Send again with command "git send-email v3-*.patch ...". Please take a view on that.
Thanks.

>> ---
>>  drivers/bus/mhi/host/pci_generic.c | 43 ++++++++++++++++++++++++++++++
>>  1 file changed, 43 insertions(+)
>> 
>
>
>-- 
>With best wishes
>Dmitry

  reply	other threads:[~2024-06-28  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  7:36 [PATCH v3 1/3] bus: mhi: host: Add Foxconn SDX72 related support Slark Xiao
2024-06-28  7:51 ` Dmitry Baryshkov
2024-06-28  8:31   ` Slark Xiao [this message]
2024-06-28  8:35     ` Slark Xiao
2024-06-28  9:26       ` Dmitry Baryshkov

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=455cd5ee.86ad.1905df8bbab.Coremail.slark_xiao@163.com \
    --to=slark_xiao@163.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mhi@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=quic_jhugo@quicinc.com \
    --cc=ryazanov.s.a@gmail.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