linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
	Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Roger Quadros <rogerq@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Paul Barker <paul.barker@sancloud.com>,
	Marc Murphy <marc.murphy@sancloud.com>,
	Jason Kridner <jkridner@gmail.com>, Andrew Davis <afd@ti.com>,
	Bajjuri Praneeth <praneeth@ti.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 2/7] arm: dts: omap: Remove incorrect compatible strings from device trees
Date: Thu, 19 Jun 2025 13:28:29 +0200	[thread overview]
Message-ID: <20250619132829.76abfedb@akair> (raw)
In-Reply-To: <20250619101334.5b67741c@kmaincent-XPS-13-7390>

Am Thu, 19 Jun 2025 10:13:34 +0200
schrieb Kory Maincent <kory.maincent@bootlin.com>:

[...]
> I am wondering if I will separate my patch series, the cleaning part raises
> lots of push back.
> 
I think this is a good idea, it is usually a good thing to always clean
things up when you bring in something new, but if it becomes the main
work, it is a bit difficult. The /s/tps@/@pmic/ should be done now.
That is unquestioned.

Regards,
Andreas

  reply	other threads:[~2025-06-19 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 11:59 [PATCH v4 0/7] Add support for BeagleBone Green Eco board Kory Maincent
2025-06-17 11:59 ` [PATCH v4 1/7] dt-bindings: omap: Add missing AM33xx compatible strings Kory Maincent
2025-06-17 15:48   ` Conor Dooley
2025-06-17 11:59 ` [PATCH v4 2/7] arm: dts: omap: Remove incorrect compatible strings from device trees Kory Maincent
2025-06-18 20:41   ` Kevin Hilman
2025-06-19  8:13     ` Kory Maincent
2025-06-19 11:28       ` Andreas Kemnade [this message]
2025-06-17 11:59 ` [PATCH v4 3/7] arm: dts: omap: am335x-bone-common: Rename tps to generic pmic node Kory Maincent
2025-06-17 11:59 ` [PATCH v4 4/7] dt-bindings: omap: Add Seeed BeagleBone Green Eco Kory Maincent
2025-06-17 11:59 ` [PATCH v4 5/7] arm: dts: omap: Add support for BeagleBone Green Eco board Kory Maincent
2025-06-17 11:59 ` [PATCH v4 6/7] arm: omap2plus_defconfig: Enable TPS65219 regulator Kory Maincent
2025-06-17 11:59 ` [PATCH v4 7/7] arm: multi_v7_defconfig: " Kory Maincent

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=20250619132829.76abfedb@akair \
    --to=andreas@kemnade.info \
    --cc=aaro.koskinen@iki.fi \
    --cc=afd@ti.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jkridner@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=kory.maincent@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marc.murphy@sancloud.com \
    --cc=paul.barker@sancloud.com \
    --cc=praneeth@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).