From: Nathan Chancellor <nathan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
"Sahin, Okan" <okan.sahin@analog.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"zzzzTilki, zzzzIbrahim" <Ibrahim.Tilki@analog.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
linux@leemhuis.info
Subject: Re: [PATCH v3 2/2] regulator: max77857: Add ADI MAX77857/59/MAX77831 Regulator Support
Date: Wed, 2 Aug 2023 16:04:26 -0700 [thread overview]
Message-ID: <20230802230426.GA3027248@dev-arch.thelio-3990X> (raw)
In-Reply-To: <32af6891-8246-46de-ba1d-ae1999f6eb10@sirena.org.uk>
On Thu, Aug 03, 2023 at 12:02:38AM +0100, Mark Brown wrote:
> On Wed, Aug 02, 2023 at 03:52:52PM -0700, Nick Desaulniers wrote:
> > Hi Okan,
> > Have you sent a follow up fix? The build should not remain broken for
> > so long. Otherwise I think Broonie should drop your patch.
>
> Someone sent what's probably a fix but I was waiting for some
> confirmation that the change actually works on hardware, it's not super
> obvious.
Got a pointer? I don't see anything on lore:
https://lore.kernel.org/all/?q=dfn:drivers/regulator/max77857-regulator.c
Cheers,
Nathan
next prev parent reply other threads:[~2023-08-02 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 5:07 [PATCH v3 0/2] Add MAX77857/59/MAX77831 Regulator Support Okan Sahin
2023-07-17 5:07 ` [PATCH v3 1/2] dt-bindings: regulator: max77857: Add ADI MAX77857/59/MAX77831 Regulator Okan Sahin
2023-07-17 5:07 ` [PATCH v3 2/2] regulator: max77857: Add ADI MAX77857/59/MAX77831 Regulator Support Okan Sahin
2023-07-18 15:55 ` Nathan Chancellor
2023-07-18 17:25 ` Sahin, Okan
2023-07-18 17:28 ` Nathan Chancellor
2023-07-18 17:38 ` Mark Brown
2023-07-26 16:10 ` Nathan Chancellor
2023-07-27 8:34 ` Sahin, Okan
2023-07-27 14:51 ` Nathan Chancellor
2023-08-02 22:52 ` Nick Desaulniers
2023-08-02 23:02 ` Mark Brown
2023-08-02 23:04 ` Nathan Chancellor [this message]
2023-08-02 23:07 ` Mark Brown
2023-08-03 9:10 ` Sahin, Okan
2023-08-03 11:15 ` Mark Brown
2023-08-03 11:33 ` Sahin, Okan
2023-07-17 13:46 ` [PATCH v3 0/2] Add " 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=20230802230426.GA3027248@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=Ibrahim.Tilki@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=okan.sahin@analog.com \
--cc=robh+dt@kernel.org \
/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