Received-SPF: pass (google.com: domain of linux-kernel+bounces-63997-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <20240213145801.2564518-1-naresh.solanki@9elements.com> <7a687805-3c99-4e1e-bad7-f40ed06ea96e@sirena.org.uk>
In-Reply-To: <7a687805-3c99-4e1e-bad7-f40ed06ea96e@sirena.org.uk>
From: Naresh Solanki <naresh.solanki@9elements.com>
Date: Tue, 13 Feb 2024 23:07:36 +0530
Message-ID: <CABqG17iDN4wtJddYOnCPYhoT0kVsTjZGEXKEzV9gSGbpu+r0Ew@mail.gmail.com>
Subject: Re: [PATCH] regulator (max5970): Fix regulator child node name
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, mazziesaccount@gmail.com, 
	linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"

Hi,


On Tue, 13 Feb 2024 at 21:07, Mark Brown <broonie@kernel.org> wrote:
>
> On Tue, Feb 13, 2024 at 08:28:00PM +0530, Naresh Solanki wrote:
> > Update regulator child node name to lower case i.e., sw0 & sw1 as
> > descibed in max5970 dt binding.
>
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
Ack.

Regards,
Naresh