From: Jonathan Cameron <jic23@kernel.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
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
Date: Sat, 6 Aug 2022 15:08:27 +0100 [thread overview]
Message-ID: <20220806150827.1b28db62@jic23-huawei> (raw)
In-Reply-To: <YueEg0tmKpc4kdLO@gmail.com>
On Mon, 1 Aug 2022 09:45:07 +0200
Marcus Folkesson <marcus.folkesson@gmail.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@gmail.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
> >
prev parent reply other threads:[~2022-08-06 13:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 13:07 [PATCH v4 0/9] Improve MCP3911 driver Marcus Folkesson
2022-07-22 13:07 ` [PATCH v4 1/9] iio: adc: mcp3911: make use of the sign bit Marcus Folkesson
2022-07-22 13:07 ` [PATCH v4 2/9] iio: adc: mcp3911: correct "microchip,device-addr" property Marcus Folkesson
2022-07-22 13:07 ` [PATCH v4 3/9] iio: adc: mcp3911: use correct formula for AD conversion Marcus Folkesson
2022-08-07 14:24 ` Jonathan Cameron
2022-07-22 13:07 ` [PATCH v4 4/9] iio: adc: mcp3911: use resource-managed version of iio_device_register Marcus Folkesson
2022-07-31 16:38 ` Jonathan Cameron
2022-07-31 16:39 ` Jonathan Cameron
2022-07-22 13:07 ` [PATCH v4 5/9] iio: adc: mcp3911: add support for buffers Marcus Folkesson
2022-07-31 16:51 ` Jonathan Cameron
2022-08-01 7:17 ` Marcus Folkesson
2022-07-22 13:07 ` [PATCH v4 6/9] iio: adc: mcp3911: add support for interrupts Marcus Folkesson
2022-07-31 16:52 ` Jonathan Cameron
2022-07-22 13:07 ` [PATCH v4 7/9] dt-bindings: iio: adc: mcp3911: add microchip,data-ready-hiz entry Marcus Folkesson
2022-07-22 13:07 ` [PATCH v4 8/9] iio: adc: mcp3911: add support for oversampling ratio Marcus Folkesson
2022-07-22 13:07 ` [PATCH v4 9/9] iio: adc: mcp3911: add support to set PGA Marcus Folkesson
2022-07-31 16:53 ` Jonathan Cameron
2022-07-31 16:41 ` [PATCH v4 0/9] Improve MCP3911 driver Jonathan Cameron
2022-08-01 7:45 ` Marcus Folkesson
2022-08-06 14:08 ` Jonathan Cameron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220806150827.1b28db62@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kent@minoris.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).