From: Trilok Soni <quic_tsoni@quicinc.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Gokul Sriram Palanisamy <quic_gokulsri@quicinc.com>,
<andersson@kernel.org>, <krzk+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <quic_viswanat@quicinc.com>, <quic_mmanikan@quicinc.com>,
<quic_varada@quicinc.com>, <quic_srichara@quicinc.com>,
<quic_gokulsri@quiconc.com>
Subject: Re: [PATCH V2 2/4] remoteproc: qcom: add hexagon based WCSS secure PIL driver
Date: Fri, 11 Oct 2024 14:51:31 -0700 [thread overview]
Message-ID: <4f11a3f8-dd77-45e8-964a-4c0935fcac8a@quicinc.com> (raw)
In-Reply-To: <b62a851c-ffb8-475a-9de1-1211a5a6b590@quicinc.com>
On 10/11/2024 12:28 PM, Jeff Johnson wrote:
> So I suspect this last line should be replaced with two:
>> + * Copyright (c) 2012-2018 The Linux Foundation. All rights reserved.
>> + * Copyright (c) 2024 Qualcomm Innovation Center, Inc. All rights reserved.
I agree.
--
---Trilok Soni
next prev parent reply other threads:[~2024-10-11 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 13:40 [PATCH V2 0/4] Add new driver for WCSS secure PIL loading Gokul Sriram Palanisamy
2024-08-29 13:40 ` [PATCH V2 1/4] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Gokul Sriram Palanisamy
2024-08-30 7:30 ` Dmitry Baryshkov
2024-09-04 10:07 ` Krzysztof Kozlowski
2024-08-29 13:40 ` [PATCH V2 2/4] remoteproc: qcom: add hexagon based WCSS secure PIL driver Gokul Sriram Palanisamy
2024-08-30 7:41 ` Dmitry Baryshkov
2025-01-03 12:08 ` Gokul Sriram P
2024-09-03 4:37 ` Kathiravan Thirumoorthy
2024-10-11 19:28 ` Jeff Johnson
2024-10-11 21:51 ` Trilok Soni [this message]
2024-08-29 13:40 ` [PATCH V2 3/4] arm64: dts: qcom: ipq5332: add nodes to bringup q6 Gokul Sriram Palanisamy
2024-10-11 19:43 ` Jeff Johnson
2024-08-29 13:40 ` [PATCH V2 4/4] arm64: dts: qcom: ipq9574: add nodes to bring up q6 Gokul Sriram Palanisamy
2024-10-11 19:43 ` Jeff Johnson
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=4f11a3f8-dd77-45e8-964a-4c0935fcac8a@quicinc.com \
--to=quic_tsoni@quicinc.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=quic_gokulsri@quicinc.com \
--cc=quic_gokulsri@quiconc.com \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_mmanikan@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=quic_viswanat@quicinc.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