linux-kernel - Re: [PATCH] regulator: hisilicon: 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: <162185754506.49496.2821074398186362162.b4-ty@kernel.org>
Date:   Mon, 24 May 2021 12:59:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Hao Fang <fanghao11@...wei.com>, puck.chen@...ilicon.com,
        guodong.xu@...aro.org, lgirdwood@...il.com
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        prime.zeng@...ilicon.com
Subject: Re: [PATCH] regulator: hisilicon: use the correct HiSilicon copyright

On Sat, 22 May 2021 18:25:51 +0800, Hao Fang wrote:
> s/Hisilicon/HiSilicon/.
> It should use capital S, according to the official website
> https://www.hisilicon.com/en.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: hisilicon: use the correct HiSilicon copyright
      commit: 8d6ee30c11a95f84974c2d7f590a7012f27b8f15

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark