linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "fanghao (A)" <fanghao11@huawei.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: <puck.chen@hisilicon.com>, <linux-kernel@vger.kernel.org>,
	<prime.zeng@hisilicon.com>
Subject: Re: [PATCH] reset: hi6220: Use the correct HiSilicon copyright
Date: Thu, 13 May 2021 10:35:00 +0800	[thread overview]
Message-ID: <a54e7ec4-7b20-0adb-151f-6e943c61d9e3@huawei.com> (raw)
In-Reply-To: <9094d229c86bd55395ad9b01ae8f5432bb80fd35.camel@pengutronix.de>



On 2021/5/12 14:19, Philipp Zabel wrote:
> On Tue, 2021-03-30 at 14:50 +0800, Hao Fang wrote:
>> s/Hisilicon/HiSilicon/g.
>> It should use capital S, according to
>> https://www.hisilicon.com/en/terms-of-use.
>>
>> Signed-off-by: Hao Fang <fanghao11@huawei.com>
>> ---
>>  drivers/reset/hisilicon/hi6220_reset.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/reset/hisilicon/hi6220_reset.c b/drivers/reset/hisilicon/hi6220_reset.c
>> index 1992650..5ca145b 100644
>> --- a/drivers/reset/hisilicon/hi6220_reset.c
>> +++ b/drivers/reset/hisilicon/hi6220_reset.c
>> @@ -3,7 +3,7 @@
>>   * Hisilicon Hi6220 reset controller driver
>
> Why leave this "Hisilicon" alone?

HiSilicon has applied for two trademarks Hisilicon/HiSilicon, so I think this one is OK. But there is only one English name for the company,
We have consulted with company's lawyer who suggested that should use a copyright statement consistent with the official website.

>
>>   *
>>   * Copyright (c) 2016 Linaro Limited.
>> - * Copyright (c) 2015-2016 Hisilicon Limited.
>> + * Copyright (c) 2015-2016 HiSilicon Limited.
>>   *
>>   * Author: Feng Chen <puck.chen@hisilicon.com>
>>   */
>
> That will be a lot of churn:
>
>   git grep Copyright.*Hisilicon | wc -l
>   141
>
>   git grep Hisilicon | wc -l
>   371

As mentioned above, I am focused on correcting the copyright.
5.13-rc1 has been released and I will continue to clean the rest by make one patch per subsystem.

Should I resend this based on 5.13-rc1?

>
> Could I get an Acked-by from someone at HiSilicon for this?

Maybe I could remind the author.

>
> regards
> Philipp
>
> .
>

Thank,
Hao


  reply	other threads:[~2021-05-13  2:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  6:50 [PATCH] reset: hi6220: Use the correct HiSilicon copyright Hao Fang
2021-05-12  6:19 ` Philipp Zabel
2021-05-13  2:35   ` fanghao (A) [this message]
2021-05-17  7:56     ` Philipp Zabel

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=a54e7ec4-7b20-0adb-151f-6e943c61d9e3@huawei.com \
    --to=fanghao11@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=prime.zeng@hisilicon.com \
    --cc=puck.chen@hisilicon.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;
as well as URLs for NNTP newsgroup(s).