linux-kernel - Re: [PATCH 2/2] regulator: max5970: Rename driver and remove wildcard

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230602081509.GO449117@google.com>
Date:   Fri, 2 Jun 2023 09:15:09 +0100
From:   Lee Jones <lee@...nel.org>
To:     Naresh Solanki <naresh.solanki@...ements.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] regulator: max5970: Rename driver and remove wildcard

On Thu, 27 Apr 2023, Naresh Solanki wrote:

> The previous version of this driver included wildcards in file names and
> descriptions. This patch renames the driver to only support MAX5970 and
> MAX5978, which are the only chips that the driver actually supports.
> 
> Signed-off-by: Naresh Solanki <Naresh.Solanki@...ements.com>
> ---
>  drivers/regulator/Kconfig                     |   6 +-
>  drivers/regulator/Makefile                    |   2 +-
>  ...ax597x-regulator.c => max5970-regulator.c} | 126 +++++++++---------
>  3 files changed, 67 insertions(+), 67 deletions(-)
>  rename drivers/regulator/{max597x-regulator.c => max5970-regulator.c} (76%)

This does not apply cleanly.  Rather than mess you around, I'll apply
the MFD driver and provide a PR for Mark.  Perhaps this will apply to
the regulator tree.

Testing now - please stand-by.

-- 
Lee Jones [李琼斯]