From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Ninad Naik <quic_ninanaik@quicinc.com>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>
Cc: <psodagud@quicinc.com>, <quic_ppareek@quicinc.com>,
<quic_kprasan@quicinc.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <kernel@quicinc.com>
Subject: Re: [RFC PATCH 1/1] soc: qcom: Add driver to read secondary bootloader (XBL) log
Date: Tue, 22 Aug 2023 08:14:51 -0700 [thread overview]
Message-ID: <c45b35cd-3906-442c-b99e-a6c06a0c5994@quicinc.com> (raw)
In-Reply-To: <39ce6d07-7692-7194-b153-e73ba7fb687c@linaro.org>
On 8/22/2023 5:43 AM, Bryan O'Donoghue wrote:
> On 22/08/2023 13:15, Ninad Naik wrote:
..snip..
>> +// SPDX-License-Identifier: GPL-2.0-only
>> +/*
>> + * Copyright (c) 2021, The Linux Foundation. All rights reserved.
>> + */
>
> 2023
if this is derived work based upon existing downstream code then I
suspect the LF 2021 copyright is correct and should be maintained, and a
QuIC 2023 copyright should be added
next prev parent reply other threads:[~2023-08-22 15:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:15 [RFC PATCH 0/1] " Ninad Naik
2023-08-22 12:15 ` [RFC PATCH 1/1] soc: qcom: " Ninad Naik
2023-08-22 12:39 ` Pavan Kondeti
2023-08-23 11:06 ` Ninad Naik
2023-08-22 12:43 ` Bryan O'Donoghue
2023-08-22 15:14 ` Jeff Johnson [this message]
2023-08-23 11:08 ` Ninad Naik
2023-08-23 11:08 ` Ninad Naik
2023-08-22 13:41 ` Srinivas Kandagatla
2023-08-23 11:09 ` Ninad Naik
2023-08-22 16:08 ` Trilok Soni
2023-08-23 11:16 ` Ninad Naik
2023-08-23 19:32 ` Trilok Soni
2023-08-28 17:19 ` [RFC PATCH 0/1] " Arun Kumar Neelakantam
2023-08-28 18:44 ` Trilok Soni
2023-08-28 19:20 ` Bjorn Andersson
2023-09-12 16:08 ` Nikunj Kela
2023-09-12 16:11 ` Trilok Soni
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=c45b35cd-3906-442c-b99e-a6c06a0c5994@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psodagud@quicinc.com \
--cc=quic_kprasan@quicinc.com \
--cc=quic_ninanaik@quicinc.com \
--cc=quic_ppareek@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
all inboxes | Powered by JetHome®