From: Sergey Ryazanov <ryazanov.s.a@gmail.com>
To: Jinjian Song <songjinjian@hotmail.com>
Cc: pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, johannes@sipsolutions.net,
loic.poulain@linaro.org, ricardo.martinez@linux.intel.com,
m.chetan.kumar@linux.intel.com, haijun.liu@mediatek.com,
chiranjeevi.rapolu@linux.intel.com,
chandrashekar.devegowda@intel.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [net-next v2 0/2] net: wwan: t7xx: Add t7xx debug port
Date: Wed, 26 Jun 2024 00:10:07 +0300 [thread overview]
Message-ID: <62976019-1e36-4e2b-a0e1-9053abaa658c@gmail.com> (raw)
In-Reply-To: <SYBP282MB35285822CB2270DAC2533DF0BBD52@SYBP282MB3528.AUSP282.PROD.OUTLOOK.COM>
Hi Jinjian,
On 25.06.2024 11:45, Jinjian Song wrote:
> Add support for t7xx WWAN device to debug by ADB (Android Debug Bridge)
> port and MTK MIPCi (Modem Information Process Center) port.
>
> Application can use ADB (Android Debg Bridge) port to implement
> functions (shell, pull, push ...) by ADB protocol commands.
>
> Application can use MIPC (Modem Information Process Center) port
> to debug antenna tunner or noise profiling through this MTK modem
> diagnostic interface.
It looks like the mail server mangled the message id. Id supposed to be
'20240625084518.10041-1-songjinjian@hotmail.com', but it was replaced by
'SYBP282MB35285822CB2270DAC2533DF0BBD52@SYBP282MB3528.AUSP282.PROD.OUTLOOK.COM'.
So, the messages chain become broken. Could you check it please?
--
Sergey
prev parent reply other threads:[~2024-06-25 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 8:45 Jinjian Song
2024-06-25 21:10 ` Sergey Ryazanov [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=62976019-1e36-4e2b-a0e1-9053abaa658c@gmail.com \
--to=ryazanov.s.a@gmail.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chiranjeevi.rapolu@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haijun.liu@mediatek.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ricardo.martinez@linux.intel.com \
--cc=songjinjian@hotmail.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
all inboxes | Powered by JetHome®