Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Conor Dooley <conor@kernel.org>,
	Frank.Li@oss.nxp.com,
	 Support Opensource <support.opensource@diasemi.com>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	 "open list:MULTIFUNCTION DEVICES (MFD)" <mfd@lists.linux.dev>,
	 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052
Date: Thu, 3 Sep 2026 12:06:51 +0200	[thread overview]
Message-ID: <20260903-vague-sassy-cow-d2d6c8@quoll> (raw)
In-Reply-To: <20260903090625.GI2133376@google.com>

On Thu, Sep 03, 2026 at 10:06:25AM +0100, Lee Jones wrote:
> On Wed, 02 Sep 2026, Conor Dooley wrote:
> 
> > On Wed, Sep 02, 2026 at 11:25:32AM +0100, Lee Jones wrote:
> > > On Tue, 01 Sep 2026, Conor Dooley wrote:
> > > 
> > > > On Mon, Aug 31, 2026 at 04:15:21PM -0400, Frank.Li@oss.nxp.com wrote:
> > > > > From: Frank Li <Frank.Li@nxp.com>
> > > > > 
> > > > > Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
> > > > > years) check_dtbs warnings:
> > > > >   arch/arm/boot/dts/nxp/imx/imx53-voipac-bsb.dtb: dialog@48 (dlg,da9053-aa): compatible: ['dlg,da9053-aa', 'dlg,da9052'] is too long
> > > > >         from schema $id: http://devicetree.org/schemas/mfd/dlg,da9052.yaml
> > > > > 
> > > > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > > > > ---
> > > > > Previous try drop dlg,da9052 at
> > > > > https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/
> > > > > 
> > > > > but Krzy have concern about compablity.
> > > > > 
> > > > > https://lore.kernel.org/imx/20251107-matrimony-showdown-ba6ce6996b2f@spud/
> > > > > 
> > > > > Conor prefer update old dts.
> > > > 
> > > > I don't think these devices are actually compatible, so this fallback
> > > > would be wrong.
> > > > The data comes from the match data, be that spi or i2c, and there's
> > > > explicitly different behaviour for the da9052 and da9053aa.
> > > > I doubt the legacy platform ever worked properly, and this is what should
> > > > have been explained in the PR that Krzysztof denied not just blindly
> > > > citing a dtbs_check problem.
> > > > 
> > > > Nacked-by: Conor Dooley <conor.dooley@microchip.com>
> > > 
> > > At first glance this looks like an Acked-by.
> > > 
> > > IMHO, this is going to cause issues - please rethink this.
> > 
> > As in, use NAKed-by instead or just say NAK without the name/mail?
> > Not entirely sure what you're getting at.
> 
> As in, don't make NACKs looks like acceptance trailers.
> 
> If you're going to "NACK", which I always felt was a bit harsh anyway,
> just say it without making it appear like an official sign-off.  Please.

Heh, tag is correct if maintainer, e.g. you in this case, would like to
take such patch still. There were already such cases, I did it once as
well to express that I do not agree with the approach taken by other
maintainer and I want to be sure that a commit in git history will never
be used in future discussions against my review (because this happens
all the time "I found commit like this, so I can add here poor code").

Best regards,
Krzysztof


  reply	other threads:[~2026-09-03 10:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 20:15 [PATCH 1/1] dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052 Frank.Li
2026-08-31 21:41 ` sashiko-bot
2026-09-01 17:00 ` Conor Dooley
2026-09-02 10:25   ` Lee Jones
2026-09-02 17:01     ` Conor Dooley
2026-09-03  9:06       ` Lee Jones
2026-09-03 10:06         ` Krzysztof Kozlowski [this message]
2026-09-03 11:36           ` Lee Jones
2026-09-03 10:04   ` Krzysztof Kozlowski
2026-09-03 15:34     ` Conor Dooley
2026-09-03 19:15     ` Frank Li
2026-09-03  9:58 ` Krzysztof Kozlowski
2026-09-03 19:22   ` Frank Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260903-vague-sassy-cow-d2d6c8@quoll \
    --to=krzk@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=Frank.Li@oss.nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=support.opensource@diasemi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox