Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 1 Aug 2022 09:45:07 +0200
From:   Marcus Folkesson <marcus.folkesson@gmail.com>
To:     Jonathan Cameron <jic23@kernel.org>
Cc:     Kent Gustavsson <kent@minoris.se>,
        Lars-Peter Clausen <lars@metafoo.de>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Andy Shevchenko <andy.shevchenko@gmail.com>,
        linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/9] Improve MCP3911 driver
Message-ID: <YueEg0tmKpc4kdLO@gmail.com>
References: <20220722130726.7627-1-marcus.folkesson@gmail.com>
 <20220731174112.072345e3@jic23-huawei>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="W/hEucp5LQz60B6z"
Content-Disposition: inline
In-Reply-To: <20220731174112.072345e3@jic23-huawei>
Precedence: bulk


--W/hEucp5LQz60B6z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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@gmail.com> wrote:
>=20
> > Hi,
> >=20
> > 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)
> >=20
> > Among the bug fixes, there are changes in the formula for calculate raw
> > value and a fix for mismatch in the devicetree property.
> >=20
> > Another general improvement for the driver is to use managed resources
> > for all allocated resources.
> >=20
> Hi Marcus,
>=20
> 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.
>=20
> 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?

Thanks,
Marcus Folkesson

>=20
> Jonathan
>=20

--W/hEucp5LQz60B6z
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBVGi6LZstU1kwSxliIBOb1ldUjIFAmLnhH4ACgkQiIBOb1ld
UjKmEg//cqbYKmFpcnaOrWMfyZOZHbWE7RbHs+5DupY019C250WBr+p/esK/vNJU
IsY2r2eHswuxECGCAU4BytjWcNDqLLSOZbewyJC5Xc6KhFZ/jmpsBjPPvr0ifSgd
H+kFkuNuXWAuXwekJHycgyveghSpP3GhqFUR435pDrQhaW7Vqt9yiGccwqYcaE2n
DJc7xkjYXF2k+KoNRwZ4LaDqUX/4450+wlHgBI6FRFMDESCdui9wXPl/D5tULYo1
kGogWuZtwjYXW+Fjn5zsIwoNwJPZixNQl1pXQFd2TSoCtWM90ZcVHqMSkvuvZYTb
fAOuv60VOXGvbB6yNPKPnnGL0JEOFeKXxRulm/Cn2nOTD2483wdR80DYChMuaHUL
Y+OE9DVTz1sUXhW9Oae4af7A7CS6T5zxX5a3TjbmgjzPCs5FlfHOqpXf5AR9AzSp
vEvyXTmyagLrFsDcxaAmEog7zFafWi4hnl4dgKdHTa5SfbHC2ws14BiyHZuk4zyx
2Xqk1picambN3kaL3TbTGMruWFrgRVhav9GM4PBZZyGnx37pcB7UqEGu6Yea8nm6
/sib0CgxwSmyXmg3kr9HxtGOOo7bADe4JK2MvJ9tHhz4oR37ruxS2E2SUI75Mlaf
dA1kvXTzu1MwOEvEyRcRpcH2B2A+Dodmqjn7BqHtcFi7Z9lAQ/k=
=xvHz
-----END PGP SIGNATURE-----

--W/hEucp5LQz60B6z--