From: Hari Nagalla <hnagalla@ti.com>
To: "Raghavendra, Vignesh" <vigneshr@ti.com>, <andersson@kernel.org>,
<devicetree@vger.kernel.org>, <mathieu.poirier@linaro.org>,
<p.zabel@pengutronix.de>, <linux-remoteproc@vger.kernel.org>,
<robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <s-anna@ti.com>
Cc: <praneeth@ti.com>, <nm@ti.com>, <a-bhatia1@ti.com>,
<j-luthra@ti.com>, <devarsht@ti.com>
Subject: Re: [PATCH 2/2] remoteproc: k3-c7x: Add support for C7xv DSP on AM62A SoC
Date: Fri, 30 Dec 2022 07:22:28 -0600 [thread overview]
Message-ID: <8b954442-40cd-1b2a-3682-248496e38462@ti.com> (raw)
In-Reply-To: <617decfc-bab6-2ba9-53de-c9a0462a2c2a@ti.com>
On 12/28/22 07:32, Raghavendra, Vignesh wrote:
>> with anlytics engine for deep leraning purposes. The remoteproc
>> handling for device management is similar to the C66/C71 DSPs on K3
>> J7 family SoCs, even though there are additional hardware accelerators
>> and IP updates to C7xv subsystem.
>>
>> Signed-off-by: Hari Nagalla<hnagalla@ti.com>
>> Signed-off-by: Jai Luthra<j-luthra@ti.com>
>> ---
> Signed-off-by of submitter should be at the last.
>
> I see original author of the patch is Jai here. So you need to amend the
> patch such that original author is set to Jai. His Signed-off-by should
> be the first and then yours.
>
Thanks for pointing it out. Fixed, sending v2 with the corrections.
prev parent reply other threads:[~2022-12-30 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 12:36 [PATCH 0/2] Add C7xv DSP for AM62A Hari Nagalla
2022-12-28 12:36 ` [PATCH 1/2] dt-bindings: remoteproc: k3-dsp: update bindings for AM62A SoCs Hari Nagalla
2022-12-28 12:38 ` Krzysztof Kozlowski
2022-12-30 13:21 ` Hari Nagalla
2022-12-28 17:16 ` Rob Herring
2022-12-28 12:36 ` [PATCH 2/2] remoteproc: k3-c7x: Add support for C7xv DSP on AM62A SoC Hari Nagalla
2022-12-28 13:32 ` Raghavendra, Vignesh
2022-12-30 13:22 ` Hari Nagalla [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=8b954442-40cd-1b2a-3682-248496e38462@ti.com \
--to=hnagalla@ti.com \
--cc=a-bhatia1@ti.com \
--cc=andersson@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-luthra@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=vigneshr@ti.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®