[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y6SIOpsxNdezKCTc@kroah.com>
Date: Thu, 22 Dec 2022 17:39:22 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Gatien Chevallier <gatien.chevallier@...s.st.com>
Cc: alexandre.torgue@...s.st.com, robh+dt@...nel.org,
Oleksii_Moisieiev@...m.com, linus.walleij@...aro.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
loic.pallardy@...com, devicetree@...r.kernel.org,
mark.rutland@....com, arnd@...db.de
Subject: Re: [RFC PATCH v2 0/7] Introduce STM32 system bus
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
Powered by blists - more mailing lists