From: Rob Herring <robh@kernel.org>
To: Gatien Chevallier <gatien.chevallier@foss.st.com>
Cc: mchehab@kernel.org, rcsekar@samsung.com,
olivier.moysan@foss.st.com, Frank Rowand <frowand.list@gmail.com>,
dmaengine@vger.kernel.org, linux-crypto@vger.kernel.org,
jic23@kernel.org, lars@metafoo.de, mkl@pengutronix.de,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
davem@davemloft.net, conor+dt@kernel.org,
fabrice.gasnier@foss.st.com, pabeni@redhat.com,
linux-media@vger.kernel.org, catalin.marinas@arm.com,
netdev@vger.kernel.org, Oleksii_Moisieiev@epam.com,
linux-serial@vger.kernel.org, hugues.fruchet@foss.st.com,
linux-usb@vger.kernel.org, linux-mmc@vger.kernel.org,
arnd@kernel.org, linux-iio@vger.kernel.org, will@kernel.org,
edumazet@google.com, linux-stm32@st-md-mailman.stormreply.com,
krzysztof.kozlowski+dt@linaro.org, ulf.hansson@linaro.org,
alexandre.torgue@foss.st.com, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org, herbert@gondor.apana.org.au,
vkoul@kernel.org, robh+dt@kernel.org, kuba@kernel.org,
wg@grandegger.com, lee@kernel.org, peng.fan@oss.nxp.com,
linux-phy@lists.infradead.org, arnaud.pouliquen@foss.st.com,
gregkh@linuxfoundation.org, richardcochran@gmail.com,
linux-arm-kernel@lists.infradead.org, andi.shyti@kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v8 06/13] of: property: fw_devlink: Add support for "access-controller"
Date: Thu, 21 Dec 2023 16:01:11 -0600 [thread overview]
Message-ID: <170319607084.165973.14576693798188042387.robh@kernel.org> (raw)
In-Reply-To: <20231212152356.345703-7-gatien.chevallier@foss.st.com>
On Tue, 12 Dec 2023 16:23:49 +0100, Gatien Chevallier wrote:
> Allows tracking dependencies between devices and their access
> controller.
>
> Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
> ---
>
> Changes in V6:
> - Renamed access-controller to access-controllers
>
> Changes in V5:
> - Rename feature-domain* to access-control*
>
> Patch not present in V1
>
> drivers/of/property.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2023-12-21 22:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 15:23 [PATCH v8 00/13] Introduce STM32 Firewall framework Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 01/13] dt-bindings: document generic access controllers Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 02/13] dt-bindings: treewide: add access-controllers description Gatien Chevallier
2024-02-03 20:47 ` Wolfram Sang
2023-12-12 15:23 ` [PATCH v8 03/13] dt-bindings: bus: document RIFSC Gatien Chevallier
[not found] ` <20231221215316.GA155023-robh@kernel.org>
2024-01-05 8:19 ` Gatien CHEVALLIER
2023-12-12 15:23 ` [PATCH v8 04/13] dt-bindings: bus: document ETZPC Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 05/13] firewall: introduce stm32_firewall framework Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 06/13] of: property: fw_devlink: Add support for "access-controller" Gatien Chevallier
2023-12-21 22:01 ` Rob Herring [this message]
2023-12-12 15:23 ` [PATCH v8 07/13] bus: rifsc: introduce RIFSC firewall controller driver Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 08/13] arm64: dts: st: add RIFSC as an access controller for STM32MP25x boards Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 09/13] bus: etzpc: introduce ETZPC firewall controller driver Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 10/13] ARM: dts: stm32: add ETZPC as a system bus for STM32MP15x boards Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 11/13] ARM: dts: stm32: put ETZPC as an access controller " Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 12/13] ARM: dts: stm32: add ETZPC as a system bus for STM32MP13x boards Gatien Chevallier
2023-12-12 15:23 ` [PATCH v8 13/13] ARM: dts: stm32: put ETZPC as an access controller " Gatien Chevallier
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=170319607084.165973.14576693798188042387.robh@kernel.org \
--to=robh@kernel.org \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alsa-devel@alsa-project.org \
--cc=andi.shyti@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=arnd@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=frowand.list@gmail.com \
--cc=gatien.chevallier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=hugues.fruchet@foss.st.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=olivier.moysan@foss.st.com \
--cc=pabeni@redhat.com \
--cc=peng.fan@oss.nxp.com \
--cc=rcsekar@samsung.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vkoul@kernel.org \
--cc=wg@grandegger.com \
--cc=will@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