From: Haixu Cui <quic_haixcui@quicinc.com>
To: Harald Mommer <harald.mommer@oss.qualcomm.com>,
<quic_msavaliy@quicinc.com>, <broonie@kernel.org>,
<virtio-dev@lists.linux.dev>, <viresh.kumar@linaro.org>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<hdanton@sina.com>, <qiang4.zhang@linux.intel.com>,
<alex.bennee@linaro.org>
Cc: <quic_ztu@quicinc.com>, <matti@qti.qualcomm.com>
Subject: Re: [RFC PATCH v6 2/3] virtio-spi: Add virtio-spi.h
Date: Thu, 7 Aug 2025 17:16:19 +0800 [thread overview]
Message-ID: <436fc0d5-2959-4364-93b4-7a14d8e2cb99@quicinc.com> (raw)
In-Reply-To: <d962ed41-2566-432d-975d-9bab8d844c70@oss.qualcomm.com>
On 7/30/2025 8:31 PM, Harald Mommer wrote:
>
> Policy was to keep the old OpenSynergy copyright notice when up-streaming started when up-streaming started in OpenSynergy times. This is also the case here with those files.
>
> The old "Copyright (C) 2023 OpenSynergy GmbH" still present in V3 must probably be kept on top of the Qualcomm copyright line.
>
> Re-checked this in virtio_rtc_driver.c from my colleague who also transitioned from OpenSynergy to Qualcomm. Virtio RTC has landed in the meantime in the mainline kernel.
>
> What's for sure is that this has not started in 2025.
Hi Harald,
I've restored the "Copyright (C) 2023 OpenSynergy GmbH" in latest
patch v8, please check, thanks.
Haixu Cui
next prev parent reply other threads:[~2025-08-07 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 9:27 [RFC PATCH v6 0/3] Virtio SPI Linux driver Haixu Cui
2025-07-24 9:27 ` [RFC PATCH v6 1/3] virtio: Add ID for virtio SPI Haixu Cui
2025-07-24 9:27 ` [RFC PATCH v6 2/3] virtio-spi: Add virtio-spi.h Haixu Cui
2025-07-30 12:31 ` Harald Mommer
2025-08-07 9:16 ` Haixu Cui [this message]
2025-07-24 9:27 ` [RFC PATCH v6 3/3] SPI: Add virtio SPI driver Haixu Cui
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=436fc0d5-2959-4364-93b4-7a14d8e2cb99@quicinc.com \
--to=quic_haixcui@quicinc.com \
--cc=alex.bennee@linaro.org \
--cc=broonie@kernel.org \
--cc=harald.mommer@oss.qualcomm.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=matti@qti.qualcomm.com \
--cc=qiang4.zhang@linux.intel.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.linux.dev \
/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®