From: Kever Yang <kever.yang@rock-chips.com>
To: Andy Yan <andyshrk@163.com>,
kishon@kernel.org, linux-phy@lists.infradead.org,
vkoul@kernel.org
Cc: heiko@sntech.de, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
sebastian.reichel@collabora.com,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH] phy: rockchip: phy-rockchip-typec: Fix Copyright description
Date: Mon, 16 Dec 2024 11:40:46 +0800 [thread overview]
Message-ID: <69751cb9-006b-485b-b3da-b8d2788d519a@rock-chips.com> (raw)
In-Reply-To: <20241215092441.3447155-1-andyshrk@163.com>
On 2024/12/15 17:24, Andy Yan wrote:
> From: Andy Yan <andy.yan@rock-chips.com>
>
> The company name has update to Rockchip Electronics Co., Ltd.
> since 2021.
> And change Co.Ltd to Co., Ltd. to fix mail server warning:
> DBL_SPAM(6.50)[co.ltd:url];
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
Thanks,
- Kever
> ---
>
> drivers/phy/rockchip/phy-rockchip-typec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/rockchip/phy-rockchip-typec.c b/drivers/phy/rockchip/phy-rockchip-typec.c
> index 122ae0fdc785..7b1dba252ce9 100644
> --- a/drivers/phy/rockchip/phy-rockchip-typec.c
> +++ b/drivers/phy/rockchip/phy-rockchip-typec.c
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0-only
> /*
> - * Copyright (C) Fuzhou Rockchip Electronics Co.Ltd
> + * Copyright (c) Rockchip Electronics Co., Ltd.
> * Author: Chris Zhong <zyw@rock-chips.com>
> * Kever Yang <kever.yang@rock-chips.com>
> *
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-12-16 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 9:24 [PATCH] phy: rockchip: phy-rockchip-typec: Fix Copyright description Andy Yan
2024-12-16 3:40 ` Kever Yang [this message]
2024-12-16 8:06 ` Heiko Stübner
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=69751cb9-006b-485b-b3da-b8d2788d519a@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sebastian.reichel@collabora.com \
--cc=vkoul@kernel.org \
/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