Re: [PATCH v1 29/33] regulator/drivers/max8976: Switch to new of thermal API

From: Mark Brown <broonie@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linexp.org>
Cc: daniel.lezcano@linaro.org, rafael@kernel.org,
	rui.zhang@intel.com, khilman@baylibre.com, abailon@baylibre.com,
	amitk@kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v1 29/33] regulator/drivers/max8976: Switch to new of thermal API
Date: Mon, 11 Jul 2022 12:02:44 +0100	[thread overview]
Message-ID: <YswDVLI+xQJGfYHF@sirena.org.uk> (raw)
In-Reply-To: <20220710212423.681301-30-daniel.lezcano@linexp.org>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Sun, Jul 10, 2022 at 11:24:19PM +0200, Daniel Lezcano wrote:
> The thermal OF code has a new API allowing to migrate the OF
> initialization to a simpler approach.

You've not copied me on the rest of the series so I've no idea what's
going on with dependencies.  When sending a patch series it is important
to ensure that all the various maintainers understand what the
relationship between the patches as the expecation is that there will be
interdependencies.  Either copy everyone on the whole series or at least
copy them on the cover letter and explain what's going on.  If there are
no strong interdependencies then it's generally simplest to just send
the patches separately to avoid any possible confusion.

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]