linux-kernel - Re: [PATCH] mmc: dw_mmc-k3: use the correct HiSilicon copyright

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPDyKFrBh+nMUB62nzTS4_6dVjEV9gVPP-X3un_DQ7rGLw2vUA@mail.gmail.com>
Date:   Wed, 31 Mar 2021 14:51:52 +0200
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     "fanghao (A)" <fanghao11@...wei.com>
Cc:     Jaehoon Chung <jh80.chung@...sung.com>,
        linux-mmc <linux-mmc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        prime.zeng@...ilicon.com
Subject: Re: [PATCH] mmc: dw_mmc-k3: use the correct HiSilicon copyright

On Tue, 30 Mar 2021 at 16:27, fanghao (A) <fanghao11@...wei.com> wrote:
>
>
>
> On 2021/3/30 18:38, Ulf Hansson wrote:
> > On Tue, 30 Mar 2021 at 08:43, Hao Fang <fanghao11@...wei.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@...wei.com>
> >> ---
> >>  drivers/mmc/host/dw_mmc-k3.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/mmc/host/dw_mmc-k3.c b/drivers/mmc/host/dw_mmc-k3.c
> >> index 29d2494..0311a37 100644
> >> --- a/drivers/mmc/host/dw_mmc-k3.c
> >> +++ b/drivers/mmc/host/dw_mmc-k3.c
> >> @@ -1,7 +1,7 @@
> >>  // SPDX-License-Identifier: GPL-2.0-or-later
> >>  /*
> >>   * 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?
> >
>
> Although HiSilicon has applied for two trademarks Hisilicon/HiSilicon,
> 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.
>
> Though the kernel has tons of "Hisilicon", I just fix the copyright,
> and plan to send a commit to each subsystem where is uncorrect. Fortunately,
> there are not many modules that have the problem, this is one of them.

git grep Hisilicon | grep Copyright | nl
gives 159 cases.

Although if you make one patch per subsystem that should be a lot
less, which seems like a reasonable approach to me.

[...]

So, applied for next, thanks!

Kind regards
Uffe