From: Greg KH <gregkh@linuxfoundation.org>
To: Gatien Chevallier <gatien.chevallier@foss.st.com>
Cc: Oleksii_Moisieiev@epam.com, herbert@gondor.apana.org.au,
davem@davemloft.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
alexandre.torgue@foss.st.com, vkoul@kernel.org, jic23@kernel.org,
olivier.moysan@foss.st.com, arnaud.pouliquen@foss.st.com,
mchehab@kernel.org, fabrice.gasnier@foss.st.com,
andi.shyti@kernel.org, ulf.hansson@linaro.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
hugues.fruchet@foss.st.com, lee@kernel.org, will@kernel.org,
catalin.marinas@arm.com, arnd@kernel.org,
richardcochran@gmail.com, Frank Rowand <frowand.list@gmail.com>,
peng.fan@oss.nxp.com, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-iio@vger.kernel.org,
alsa-devel@alsa-project.org, linux-media@vger.kernel.org,
linux-mmc@vger.kernel.org, netdev@vger.kernel.org,
linux-phy@lists.infradead.org, linux-serial@vger.kernel.org,
linux-spi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [IGNORE][PATCH v4 01/11] dt-bindings: Document common device controller bindings
Date: Fri, 11 Aug 2023 12:16:44 +0200 [thread overview]
Message-ID: <2023081117-sprout-cruncher-862c@gregkh> (raw)
In-Reply-To: <20230811100731.108145-2-gatien.chevallier@foss.st.com>
On Fri, Aug 11, 2023 at 12:07:21PM +0200, Gatien Chevallier wrote:
> From: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>
>
> Introducing of the common device controller bindings for the controller
> provider and consumer devices. Those bindings are intended to allow
> divided system on chip into multiple domains, that can be used to
> configure hardware permissions.
>
> Signed-off-by: Oleksii Moisieiev <oleksii_moisieiev@epam.com>
> [Gatien: Fix typos and YAML error]
> Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
> ---
>
> Changes in V4:
> Corrected typos and YAML errors
Why are we supposed to ignore the first patch in this series, but pay
attention to the 10 after this that depend on it?
totally confused,
greg k-h
next prev parent reply other threads:[~2023-08-11 10:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 10:07 [PATCH v4 00/11] Introduce STM32 Firewall framework Gatien Chevallier
2023-08-11 10:07 ` [IGNORE][PATCH v4 01/11] dt-bindings: Document common device controller bindings Gatien Chevallier
2023-08-11 10:16 ` Greg KH [this message]
2023-08-11 12:00 ` Gatien CHEVALLIER
2023-09-29 13:18 ` Gatien CHEVALLIER
2023-08-11 10:07 ` [PATCH v4 02/11] dt-bindings: treewide: add feature-domains description Gatien Chevallier
2023-08-14 13:45 ` Wolfram Sang
2023-08-11 10:07 ` [PATCH v4 03/11] dt-bindings: bus: document RIFSC Gatien Chevallier
2023-08-11 10:07 ` [PATCH v4 04/11] dt-bindings: bus: document ETZPC Gatien Chevallier
2023-08-11 10:07 ` [PATCH v4 05/11] firewall: introduce stm32_firewall framework Gatien Chevallier
2023-08-12 14:09 ` Simon Horman
2023-09-28 15:43 ` Gatien CHEVALLIER
2023-08-11 10:07 ` [PATCH v4 06/11] of: property: fw_devlink: Add support for "feature-domains" Gatien Chevallier
2023-08-11 10:07 ` [PATCH v4 07/11] bus: rifsc: introduce RIFSC firewall controller driver Gatien Chevallier
2023-08-11 10:07 ` [PATCH v4 08/11] arm64: dts: st: add RIFSC as a domain controller for STM32MP25x boards Gatien Chevallier
2023-08-11 10:07 ` [PATCH v4 09/11] bus: etzpc: introduce ETZPC firewall controller driver Gatien Chevallier
2023-08-11 10:07 ` [PATCH v4 10/11] ARM: dts: stm32: add ETZPC as a system bus for STM32MP15x boards Gatien Chevallier
2023-08-11 10:07 ` [PATCH v4 11/11] ARM: dts: stm32: add ETZPC as a system bus for STM32MP13x boards 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=2023081117-sprout-cruncher-862c@gregkh \
--to=gregkh@linuxfoundation.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=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=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=netdev@vger.kernel.org \
--cc=olivier.moysan@foss.st.com \
--cc=pabeni@redhat.com \
--cc=peng.fan@oss.nxp.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vkoul@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).