From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio <linux-iio@vger.kernel.org>,
Peter Rosin <peda@axentia.se>,
Michael Hennerich <michael.hennerich@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: Re: [PATCH v2 16/17] iio: cdc: ad7746: Move driver out of staging.
Date: Mon, 20 Jun 2022 20:53:22 +0100 [thread overview]
Message-ID: <20220620205322.737f4a57@jic23-huawei> (raw)
In-Reply-To: <CAHp75Vd6V0-h82MmDfwWa5e_0_DD1-S7jAmse-fhiAc2nmRc_w@mail.gmail.com>
On Mon, 20 Jun 2022 20:40:17 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Mon, Jun 20, 2022 at 6:40 PM Jonathan Cameron
> <Jonathan.Cameron@huawei.com> wrote:
> > On Mon, 20 Jun 2022 01:11:36 +0200
> > Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > > On Sun, Jun 19, 2022 at 8:59 PM Jonathan Cameron <jic23@kernel.org> wrote:
>
> ...
>
> > > > drivers/iio/cdc/ad7746.c | 818 +++++++++++++++++++++++++++++++
> > > > drivers/staging/iio/cdc/ad7746.c | 818 -------------------------------
> > >
> > > It's a bit hard to review, perhaps you forgot to add -M -C when
> > > generating this patch?
> >
> > Specifically passed --no-renames because this is a direct file move -
> > I should have stated that though.
> >
> > The intent is to allow review of the full driver as being proposed for
> > move out of staging.
>
> In (my) practice it only makes review much harder without any
> additional benefits. Git is smart to understand renaming and in the
> diffstat there is a special line about renaming.
>
> > Including the bits that otherwise aren't
> > visible anywhere in the driver. I only do this (and ask for it from others)
> > for staging graduation patches.
>
> Perhaps somebody finds that useful, but me :-)
>
I definitely do as lets me lazy and not apply the patches just do a review
+ where do you comment on something in the original driver that is getting moved?
That particularly use case only really applies to drivers moving out of staging
though. Alternative is to paste the entire driver in the cover letter which
is not a great solution either...
Jonathan
next prev parent reply other threads:[~2022-06-20 19:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 18:58 [PATCH v2 00/17] staging/iio: Clean up AD7746 CDC driver and move from staging Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 01/17] iio: core: Increase precision of IIO_VAL_FRACTIONAL_LOG2 when possible Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 02/17] iio: ABI: Fix wrong format of differential capacitance channel ABI Jonathan Cameron
2022-06-19 22:58 ` Andy Shevchenko
2022-06-20 17:50 ` Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 03/17] staging: iio: cdc: ad7746: Use explicit be24 handling Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 04/17] staging: iio: cdc: ad7746: Push handling of supply voltage scale to userspace Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 05/17] staging: iio: cdc: ad7746: Use local buffer for multi byte reads Jonathan Cameron
2022-06-19 23:00 ` Andy Shevchenko
2022-06-20 16:42 ` Jonathan Cameron
2022-06-20 18:23 ` Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 06/17] staging: iio: cdc: ad7746: Factor out ad7746_read_channel() Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 07/17] staging: iio: cdc: ad7764: Push locking down into case statements in read/write_raw Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 08/17] staging: iio: cdc: ad7746: Break up use of chan->address and use FIELD_PREP etc Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 09/17] staging: iio: cdc: ad7746: Drop usused i2c_set_clientdata() Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 10/17] staging: iio: cdc: ad7746: Use _raw and _scale for temperature channels Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 11/17] iio: core: Introduce _inputoffset for differential channels Jonathan Cameron
2022-06-19 23:20 ` Andy Shevchenko
2022-06-20 18:13 ` Jonathan Cameron
2022-06-20 18:35 ` Andy Shevchenko
2022-06-20 20:01 ` Jonathan Cameron
2022-06-20 19:57 ` Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 12/17] staging: iio: cdc: ad7746: Switch from _offset to " Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 13/17] staging: iio: cdc: ad7746: Use read_avail() rather than opencoding Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 14/17] staging: iio: ad7746: White space cleanup Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 15/17] iio: cdc: ad7746: Add device specific ABI documentation Jonathan Cameron
2022-06-19 18:58 ` [PATCH v2 16/17] iio: cdc: ad7746: Move driver out of staging Jonathan Cameron
2022-06-19 23:11 ` Andy Shevchenko
2022-06-20 16:40 ` Jonathan Cameron
2022-06-20 18:30 ` Jonathan Cameron
2022-06-20 18:40 ` Andy Shevchenko
2022-06-20 19:53 ` Jonathan Cameron [this message]
2022-06-20 20:01 ` Andy Shevchenko
2022-06-19 18:58 ` [PATCH v2 17/17] RFC: iio: cdc: ad7746: Add roadtest Jonathan Cameron
2022-06-19 23:23 ` [PATCH v2 00/17] staging/iio: Clean up AD7746 CDC driver and move from staging Andy Shevchenko
2022-06-20 18:07 ` Jonathan Cameron
2022-06-21 14:34 ` Joe Simmons-Talbott
2022-06-22 13:07 ` Vincent Whitchurch
2022-06-26 11:07 ` Jonathan Cameron
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=20220620205322.737f4a57@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=peda@axentia.se \
--cc=vincent.whitchurch@axis.com \
/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