linux-kernel - Re: [PATCH v4 0/9] Improve MCP3911 driver

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]

Date:   Sat, 6 Aug 2022 15:08:27 +0100
From:   Jonathan Cameron <jic23@...nel.org>
To:     Marcus Folkesson <marcus.folkesson@...il.com>
Cc:     Kent Gustavsson <kent@...oris.se>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/9] Improve MCP3911 driver

On Mon, 1 Aug 2022 09:45:07 +0200
Marcus Folkesson <marcus.folkesson@...il.com> wrote:

> On Sun, Jul 31, 2022 at 05:41:12PM +0100, Jonathan Cameron wrote:
> > On Fri, 22 Jul 2022 15:07:17 +0200
> > Marcus Folkesson <marcus.folkesson@...il.com> wrote:
> >   
> > > Hi,
> > > 
> > > This patch series intend to fix bugs and improve functionality of the
> > > MCP3911 driver.
> > > The main features added are
> > > - Support for buffers
> > > - Interrupt driven readings
> > > - Support for oversampling ratio
> > > - Support for set scale values (Gain)
> > > 
> > > Among the bug fixes, there are changes in the formula for calculate raw
> > > value and a fix for mismatch in the devicetree property.
> > > 
> > > Another general improvement for the driver is to use managed resources
> > > for all allocated resources.
> > >   
> > Hi Marcus,
> > 
> > The first 3 fixes look good to me.  Do you want me to pick those up to
> > go in after rc1 via my togreg-fixes branch?  The side effect of doing
> > that is it'll be a little while before they are upstream in the branch
> > I'll want to pick the rest of the series on top of.
> > 
> > So it's a trade off between getting fixes in as soon as possible and
> > slowing down other improvements a little.  
> 
> Both ways works for me.
> I guess it is preferable to get the fixes in as soon as possible?
> 
> If so, do you want me to rebase the series on your togreg-fixes branch
> or wait to send v5 until the patches are upstream?
> 
> Or simply keep sending the whole series?

For now resend the whole series. I don't want to pick anything up onto the fixes-togreg
branch until rc1 (as good time to get it to a more recent base).  So I'll sit on these
for another week anyway.

Thanks,


Jonathan

> 
> Thanks,
> Marcus Folkesson
> 
> > 
> > Jonathan
> >