From: "fanghao (A)" <fanghao11@huawei.com>
To: Pavel Machek <pavel@ucw.cz>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<prime.zeng@hisilicon.com>
Subject: Re: [PATCH] mmc: dw_mmc-k3: use the correct HiSilicon copyright
Date: Tue, 30 Mar 2021 22:31:24 +0800 [thread overview]
Message-ID: <dabcbb05-2d5a-f32e-a725-3dbc51c2f0d5@huawei.com> (raw)
In-Reply-To: <20210330134323.GA3700@duo.ucw.cz>
On 2021/3/30 21:43, Pavel Machek wrote:
> Hi!
>
>> On Tue, 30 Mar 2021 at 08:43, Hao Fang <fanghao11@huawei.com> 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>
>
>>> /*
>>> * Copyright (c) 2013 Linaro Ltd.
>>> - * Copyright (c) 2013 Hisilicon Limited.
>>> + * Copyright (c) 2013 HiSilicon Limited.
>>
>> This change looks really silly to me, but I am not a lawyer - so I
>> can't tell if this makes sense or not.
>>
>> In any case, "Hisilicon" is being used all over the kernel - do you
>> intend to patch all places with similar changes like this one? Perhaps
>> just send a big tree-wide-patch instead and see what people think?
>
> Plus, I'd expect authors to submit changes to copyright notices.
>
Just add Reviewed-by or Acked-by! Thanks.
> Best regards,
> Pavel
>
next prev parent reply other threads:[~2021-03-30 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 6:40 Hao Fang
2021-03-30 10:38 ` Ulf Hansson
2021-03-30 13:43 ` Pavel Machek
2021-03-30 14:31 ` fanghao (A) [this message]
2021-03-30 14:27 ` fanghao (A)
2021-03-31 12:51 ` Ulf Hansson
2021-03-31 6:59 ` Zhangfei Gao
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=dabcbb05-2d5a-f32e-a725-3dbc51c2f0d5@huawei.com \
--to=fanghao11@huawei.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=prime.zeng@hisilicon.com \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®