From: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Tue, 3 Jan 2023 10:45:15 +0100 [thread overview]
Message-ID: <98aa92e9-9ac0-0fe4-a140-ac478e261f94@foss.st.com> (raw)
In-Reply-To: <Y6SIOpsxNdezKCTc@kroah.com>
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?
Best regards,
Gatien
On 12/22/22 17:39, Greg KH wrote:
> On Thu, Dec 22, 2022 at 11:04:57AM +0100, Gatien Chevallier wrote:
>> Document STM32 System Bus. This bus is intended to control firewall
>> access for the peripherals connected to it.
>
> Why is this an "RFC"? That usually means "I have more work to do on it,
> but I'll send it out now anyway". What work is left?
>
> And for most code, I know I don't review "RFC" changes as there are too
> many "real" patches being submitted where people think their code is
> ready to be merged. Other reviewers might think otherwise, but be aware
> of this...
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-01-03 9:46 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 [this message]
2023-01-04 6:10 ` Greg KH
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=98aa92e9-9ac0-0fe4-a140-ac478e261f94@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).