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  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]
Date:   Sun, 11 Dec 2022 12:20:43 +0000
From:   Jonathan Cameron <>
To:     Andy Shevchenko <>
Cc:     Okan Sahin <>,,
        Lee Jones <>, Rob Herring <>,
        Krzysztof Kozlowski <>,
        Liam Girdwood <>,
        Mark Brown <>,
        Lars-Peter Clausen <>,
        Caleb Connolly <>,
        Ramona Bolboaca <>,
        Geert Uytterhoeven <>,
        Lad Prabhakar <>,
        ChiYuan Huang <>,
        Anand Ashok Dumbre <>,
        William Breathitt Gray <>,
        Manish Narani <>,,,
Subject: Re: [PATCH 0/5] staging: drivers: mfd: Add MAX77541 MFD and related
 device drivers

On Wed, 7 Dec 2022 13:09:34 +0200
Andy Shevchenko <> wrote:

> On Wed, Dec 07, 2022 at 12:08:39PM +0300, Okan Sahin wrote:
> > This patchset adds mfd, regulator and adc driver and related bindings.The patches 
> > are required to be applied in sequence.  
> You have an indentation / wrapping issues in the above text.
> Nevertheless, why staging? What does it mean?

The main reason to go via staging is because a driver is sitting out
of tree and it is useful to bring it in on the basis that it can then be
cleaned up in tree before moving out of staging.

For a relatively small driver like this, that's hard to argue.  Just
clean it up in response to review feedback and then we can take it
directly into relevant subsystems in the main tree.


Powered by blists - more mailing lists