Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 2 Jun 2023 09:15:09 +0100
From:   Lee Jones <lee@kernel.org>
To:     Naresh Solanki <naresh.solanki@9elements.com>
Cc:     Liam Girdwood <lgirdwood@gmail.com>,
        Mark Brown <broonie@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: max5970: Rename driver and remove wildcard
Message-ID: <20230602081509.GO449117@google.com>
References: <20230427113046.3971425-1-Naresh.Solanki@9elements.com>
 <20230427113046.3971425-2-Naresh.Solanki@9elements.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20230427113046.3971425-2-Naresh.Solanki@9elements.com>
Precedence: bulk

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@9elements.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 [李琼斯]