From: Greg KH <gregkh@linuxfoundation.org>
To: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
Cc: alexandre.torgue@foss.st.com, robh+dt@kernel.org,
Oleksii_Moisieiev@epam.com, linus.walleij@linaro.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, loic.pallardy@st.com,
devicetree@vger.kernel.org, mark.rutland@arm.com, arnd@arndb.de
Subject: Re: [RFC PATCH v2 0/7] Introduce STM32 system bus
Date: Wed, 4 Jan 2023 07:10:48 +0100 [thread overview]
Message-ID: <Y7UYaDL82NqFu7vK@kroah.com> (raw)
In-Reply-To: <98aa92e9-9ac0-0fe4-a140-ac478e261f94@foss.st.com>
On Tue, Jan 03, 2023 at 10:45:15AM +0100, Gatien CHEVALLIER wrote:
> Hello Greg,
>
> I've put the "RFC" tag on the the patch set as it is based on bindings that
> are currently under review. It has been submitted with the idea to support
> the bindings proposed by Oleksii. Apart from this and the comments made by
> Krzysztof, there is indeed no more "work" planned on this change.
>
> Should the "RFC" tag be omitted for the next version?
If you feel it is ready to be merged, yes, then please remove it,
otherwise it's obviously not ready and will not be merged :)
thanks,
greg k-h
prev parent reply other threads:[~2023-01-04 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 10:04 [RFC PATCH v2 0/7] Introduce STM32 system bus Gatien Chevallier
2022-12-22 10:04 ` [RFC PATCH v2 1/7] dt-bindings: Document common device controller bindings Gatien Chevallier
2022-12-23 10:08 ` Krzysztof Kozlowski
2022-12-22 10:04 ` [RFC PATCH v2 2/7] dt-bindings: bus: add STM32 System Bus Gatien Chevallier
2022-12-22 10:05 ` [RFC PATCH v2 3/7] dt-bindings: bus: add STM32MP15 ETZPC firewall bus bindings Gatien Chevallier
2022-12-22 10:05 ` [RFC PATCH v2 4/7] dt-bindings: bus: add STM32MP13 " Gatien Chevallier
2022-12-22 16:39 ` [RFC PATCH v2 0/7] Introduce STM32 system bus Greg KH
2023-01-03 9:45 ` Gatien CHEVALLIER
2023-01-04 6:10 ` Greg KH [this message]
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=Y7UYaDL82NqFu7vK@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gatien.chevallier@foss.st.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=loic.pallardy@st.com \
--cc=mark.rutland@arm.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