From: "fanghao (A)" <fanghao11@huawei.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, <xuezhiliang@hisilicon.com>
Cc: <xuezhiliang@huawei.com>, <linux-input@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <prime.zeng@hisilicon.com>
Subject: Re: [PATCH RESEND] Input: misc - use the correct HiSilicon copyright
Date: Mon, 24 May 2021 21:59:05 +0800 [thread overview]
Message-ID: <17af7a73-7a9f-2587-3529-bca5a7b775a2@huawei.com> (raw)
In-Reply-To: <YKsWGjy/0u/T8iO2@google.com>
On 2021/5/24 10:57, Dmitry Torokhov wrote:
> Hi Hao,
>
> On Sat, May 22, 2021 at 06:06:27PM +0800, Hao Fang wrote:
>> s/Hisilicon/HiSilicon/g.
>> It should use capital S, according to
>> https://www.hisilicon.com/en.
>>
>> Signed-off-by: Hao Fang <fanghao11@huawei.com>
>> ---
>> drivers/input/misc/hisi_powerkey.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/input/misc/hisi_powerkey.c b/drivers/input/misc/hisi_powerkey.c
>> index d3c293a..54cbfdf 100644
>> --- a/drivers/input/misc/hisi_powerkey.c
>> +++ b/drivers/input/misc/hisi_powerkey.c
>> @@ -1,7 +1,7 @@
>> /*
>> * Hisilicon PMIC powerkey driver
>> *
>> - * Copyright (C) 2013 Hisilicon Ltd.
>> + * Copyright (C) 2013 HiSilicon Ltd.
>
> I see there are various versions of "Hisilicon" in copyright notices. I
> do not know if capitalization here matters and which form is correct.
> If this is important I'd rather HiSilicon folks submitted such
> patch(es).
>
Xuezhiliang, can you help to review this patch and add an Acked-by? Or you can resubmit it.
I found out you're the author of this driver, maybe you changed your email address.
Thanks.
Hao
>
prev parent reply other threads:[~2021-05-24 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 10:06 [PATCH RESEND] Input: misc - use the correct HiSilicon copyright Hao Fang
2021-05-24 2:57 ` Dmitry Torokhov
2021-05-24 13:59 ` fanghao (A) [this message]
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=17af7a73-7a9f-2587-3529-bca5a7b775a2@huawei.com \
--to=fanghao11@huawei.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prime.zeng@hisilicon.com \
--cc=xuezhiliang@hisilicon.com \
--cc=xuezhiliang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.