From: Mark Brown <broonie@kernel.org>
To: Adrien Grassein <adrien.grassein@gmail.com>
Cc: jagan@amarulasolutions.com, lgirdwood@gmail.com,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v3 3/6] regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property
Date: Mon, 11 Jan 2021 17:20:20 +0000 [thread overview]
Message-ID: <20210111172019.GH4728@sirena.org.uk> (raw)
In-Reply-To: <20210108225006.153700-4-adrien.grassein@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
On Fri, Jan 08, 2021 at 11:50:03PM +0100, Adrien Grassein wrote:
> This property seems useless because we can use the
> regulator-max-microamp generic property to do the same
> and using generic code.
This made it into a kernel release so we should continue to honour it,
it's fine to deprecate it though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-11 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 22:50 [PATCH v3 0/6] Fix issues on pf8x00 driver Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 1/6] regulator: pf8x00: add a doc for the module Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 2/6] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc Adrien Grassein
2021-01-13 15:28 ` Rob Herring
2021-01-08 22:50 ` [PATCH v3 3/6] regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property Adrien Grassein
2021-01-11 17:20 ` Mark Brown [this message]
2021-01-11 17:27 ` Adrien Grassein
2021-01-11 17:32 ` Mark Brown
2021-01-08 22:50 ` [PATCH v3 4/6] regulator: " Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 5/6] regulator: pf8x00: use linear range for buck 1-6 Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 6/6] regulator: pf8x00: fix nxp,phase-shift Adrien Grassein
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=20210111172019.GH4728@sirena.org.uk \
--to=broonie@kernel.org \
--cc=adrien.grassein@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).