All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Rosen Penev <rosenp@gmail.com>, devicetree@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dennis Gilmore <dennis@ausil.us>,
	"moderated list:ARM/Marvell Kirkwood and Armada 370, 375,
	38x,..." <linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 0/3] ARM: dts: helios4: add regulator supplies
Date: Sun, 09 Aug 2026 12:47:55 +0200	[thread overview]
Message-ID: <871pc7muxw.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260709005005.1587852-1-rosenp@gmail.com>

Hi Rosen Penev,

> This series adds missing vcc-supply properties to the EEPROM and GPIO
> expander on the Helios4, adds SATA regulator supplies.
>
> v2: remove thermal patch
>
> Rosen Penev (3):
>   ARM: dts: helios4: add vcc-supply to EEPROM
>   ARM: dts: helios4: add vcc-supply to GPIO expander
>   ARM: dts: helios4: add SATA regulator supplies
>

Applied on mvebu/dt

Thanks,

Gregory


>  arch/arm/boot/dts/marvell/armada-388-helios4.dts | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> -- 
> 2.55.0
>

-- 
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2026-08-09 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  0:50 [PATCHv2 0/3] ARM: dts: helios4: add regulator supplies Rosen Penev
2026-07-09  0:50 ` [PATCHv2 1/3] ARM: dts: helios4: add vcc-supply to EEPROM Rosen Penev
2026-07-09  0:50 ` [PATCHv2 2/3] ARM: dts: helios4: add vcc-supply to GPIO expander Rosen Penev
2026-07-09  0:50 ` [PATCHv2 3/3] ARM: dts: helios4: add SATA regulator supplies Rosen Penev
2026-07-09  1:02   ` sashiko-bot
2026-07-12 21:34     ` Rosen Penev
2026-08-09 10:47 ` Gregory CLEMENT [this message]

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=871pc7muxw.fsf@BLaptop.bootlin.com \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=dennis@ausil.us \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rosenp@gmail.com \
    --cc=sebastian.hesselbarth@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.