From: Krzysztof Kozlowski <krzk@kernel.org>
To: Woody Douglass <wdouglass@carnegierobotics.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "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 16:07:53 +0200 [thread overview]
Message-ID: <9050a07a-e94e-4d34-b4aa-bd2e6f91f792@kernel.org> (raw)
In-Reply-To: <3c45fe88-c9f4-4606-87bc-726f262998cc@carnegierobotics.com>
On 04/09/2025 15:57, Woody Douglass wrote:
> All,
>
> When i submitted this patch, I got a bunch of "unsolicited mail" bounces from gmail. My
> @carnegierobotics.com address is an exchange server with no exposed smtp, so i have to
> send patches with `git send-email` via an envelope sender (git@douglass.dev). I suspect
> this is what caused this. I'm sorry for the inconvenience; patch v5 still seems to be
> on the lkml archive.
Maybe b4 relay will be helpful:
https://b4.docs.kernel.org/en/latest/contributor/send.html
but if you have own SMTP, then could work as well.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-04 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 13:46 [PATCH v5 0/2] regulator: pf530x: NXP PF530x regulator driver 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 [this message]
2025-09-04 14:20 ` Woody Douglass
2025-09-04 14:42 ` Mark Brown
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=9050a07a-e94e-4d34-b4aa-bd2e6f91f792@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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