mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Woody Douglass <wdouglass@carnegierobotics.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] regulator: pf530x: NXP PF530x regulator driver
Date: Thu, 4 Sep 2025 15:42:59 +0100	[thread overview]
Message-ID: <462637d8-ce9d-4ba8-a6cf-a5e59e7ffd26@sirena.org.uk> (raw)
In-Reply-To: <26fe4872-dc16-4db1-ac0a-e325222d0864@carnegierobotics.com>

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

On Thu, Sep 04, 2025 at 02:20:05PM +0000, Woody Douglass wrote:

> I will configure the web relay for future patches, thank you! Should I resubmit patch v5, or is the
> fact that it's on the lkml archive good enough? it's at
> https://lore.kernel.org/lkml/20250902-pf530x-v5-0-658c403e6a52@carnegierobotics.com/

It came through fine here so I don't need a resend.

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

      reply	other threads:[~2025-09-04 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 13:46 Woodrow Douglass
2025-09-04 13:46 ` [PATCH v5 1/2] regulator: pf530x: dt-bindings: nxp,pf530x-regulator Woodrow Douglass
2025-09-04 13:46 ` [PATCH v5 2/2] regulator: pf530x: Add a driver for the NXP PF5300 Regulator Woodrow Douglass
2025-09-04 13:57 ` [PATCH v5 0/2] regulator: pf530x: NXP PF530x regulator driver Woody Douglass
2025-09-04 14:07   ` Krzysztof Kozlowski
2025-09-04 14:20     ` Woody Douglass
2025-09-04 14:42       ` Mark Brown [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=462637d8-ce9d-4ba8-a6cf-a5e59e7ffd26@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=wdouglass@carnegierobotics.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

all inboxes | Powered by JetHome®