lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <98aa92e9-9ac0-0fe4-a140-ac478e261f94@foss.st.com>
Date:   Tue, 3 Jan 2023 10:45:15 +0100
From:   Gatien CHEVALLIER <gatien.chevallier@...s.st.com>
To:     Greg KH <gregkh@...uxfoundation.org>
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

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ