From: Mark Brown <broonie@kernel.org>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regulator: gpio: Honor regulator-boot-on property
Date: Mon, 20 Jul 2020 12:06:11 +0100 [thread overview]
Message-ID: <20200720110610.GA4601@sirena.org.uk> (raw)
In-Reply-To: <20200720100113.6481-1-wens@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 349 bytes --]
On Mon, Jul 20, 2020 at 06:01:13PM +0800, Chen-Yu Tsai wrote:
> Also drop support for the undocumented enable-at-boot property. This
> property was not documented in the original commit introducing DT
> support, nor is it now, and there are no in-tree device trees that use
> this property.
There may still be out of tree users, an ABI is an ABI.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH v2] regulator: gpio: Honor regulator-boot-on property
Date: Mon, 20 Jul 2020 12:06:11 +0100 [thread overview]
Message-ID: <20200720110610.GA4601@sirena.org.uk> (raw)
In-Reply-To: <20200720100113.6481-1-wens@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
On Mon, Jul 20, 2020 at 06:01:13PM +0800, Chen-Yu Tsai wrote:
> Also drop support for the undocumented enable-at-boot property. This
> property was not documented in the original commit introducing DT
> support, nor is it now, and there are no in-tree device trees that use
> this property.
There may still be out of tree users, an ABI is an ABI.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-20 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 10:01 [PATCH v2] regulator: gpio: Honor regulator-boot-on property Chen-Yu Tsai
2020-07-20 10:01 ` Chen-Yu Tsai
2020-07-20 11:06 ` Mark Brown [this message]
2020-07-20 11:06 ` Mark Brown
2020-07-20 12:03 ` Chen-Yu Tsai
2020-07-20 12:03 ` Chen-Yu Tsai
2020-07-20 12:04 ` Mark Brown
2020-07-20 12:04 ` 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=20200720110610.GA4601@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=wens@csie.org \
--cc=wens@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 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.