linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marek Vasut <marex@denx.de>, Stefan Wahren <stefan.wahren@i2se.com>
Cc: "Hartmut Knaack" <knaack.h@gmx.de>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Peter Meerwald" <pmeerw@pmeerw.net>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Kristina Martšenko" <kristina.martsenko@gmail.com>,
	"Fabio Estevam" <fabio.estevam@freescale.com>,
	linux-iio@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH V2 0/6] iio: mxs-lradc: Clean up and add datasheet names
Date: Sun, 19 Jul 2015 10:45:29 +0100	[thread overview]
Message-ID: <55AB71B9.8070307@kernel.org> (raw)
In-Reply-To: <201507181738.21236.marex@denx.de>

On 18/07/15 16:38, Marek Vasut wrote:
> On Saturday, July 18, 2015 at 02:30:40 PM, Stefan Wahren wrote:
>> This patch series does some clean up in mxs-lradc and finally add the
>> datasheet names for every usable channel.
>>
>> Changes in V2:
>>   - remove confusing i.MX28 specific comments
>>   - fix some spelling errors
>>   - fix up includes
>>   - separate channel spec for i.MX23 and i.MX28
>>
>> Stefan Wahren (6):
>>   iio: mxs-lradc: clarify supported devices
>>   iio: mxs-lradc: fix some spelling errors
>>   iio: mxs-lradc: add missing include
>>   iio: mxs-lradc: remove unnecessary header includes
>>   iio: mxs-lradc: reorder header includes
>>   iio: mxs-lradc: add datasheet name for every usable channel
>>
>>  .../bindings/staging/iio/adc/mxs-lradc.txt         |    2 +-
>>  drivers/staging/iio/adc/mxs-lradc.c                |  122
>> +++++++++++++------- 2 files changed, 82 insertions(+), 42 deletions(-)
> 
> Entire series
> 
> Reviewed-by: Marek Vasut <marex@denx.de>
Thanks for looking through these. 

Just to let you know, there is currently a rather extended discussion going
on (as part of a suggested topic for the kernel summit) about when reviewed-by
tags are appropriate.

The general feeling is they must in someway indicate some substantial work.  Here
as a result I'd say it was appropriate for patch 6 whereas an Acked-by 
would be more appropriate for the cleanups (where there is nothing 'interesting').
I've left these as reviewed by for this set though!

Note to all reviewers I may also start added reviewed by tags that you haven't sent if
I happen to feel you made a big contribution to review of a patch, but perhaps haven't
revisited later versions.  I'll probably send out an email about this outside
of this thread at some point to get possible wider circulation.

Jonathan
> 
> Best regards,
> Marek Vasut
> 


  reply	other threads:[~2015-07-19  9:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18 12:30 [PATCH V2 0/6] iio: mxs-lradc: Clean up and add datasheet names Stefan Wahren
2015-07-18 12:30 ` [PATCH 1/6] iio: mxs-lradc: clarify supported devices Stefan Wahren
2015-07-19  9:32   ` Jonathan Cameron
2015-07-18 12:30 ` [PATCH 2/6] iio: mxs-lradc: fix some spelling errors Stefan Wahren
2015-07-19  9:33   ` Jonathan Cameron
2015-07-18 12:30 ` [PATCH 3/6] iio: mxs-lradc: add missing include Stefan Wahren
2015-07-19  9:34   ` Jonathan Cameron
2015-07-18 12:30 ` [PATCH 4/6] iio: mxs-lradc: remove unnecessary header includes Stefan Wahren
2015-07-19  9:35   ` Jonathan Cameron
2015-07-18 12:30 ` [PATCH 5/6] iio: mxs-lradc: reorder " Stefan Wahren
2015-07-18 15:37   ` Marek Vasut
2015-07-19  9:37     ` Jonathan Cameron
2015-07-18 12:30 ` [PATCH 6/6] iio: mxs-lradc: add datasheet name for every usable channel Stefan Wahren
2015-07-19  9:40   ` Jonathan Cameron
2015-07-18 15:38 ` [PATCH V2 0/6] iio: mxs-lradc: Clean up and add datasheet names Marek Vasut
2015-07-19  9:45   ` Jonathan Cameron [this message]
2015-07-19 20:33     ` Dan Carpenter
2015-07-19 20:49       ` Dan Carpenter
2015-07-19 21:44         ` Jonathan Cameron
2015-07-19 22:06         ` Marek Vasut
2015-07-20  7:00           ` Dan Carpenter
2015-07-20  8:16             ` Marek Vasut
2015-07-19 21:08       ` Jonathan Cameron
2015-07-19 22:11     ` Marek Vasut

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=55AB71B9.8070307@kernel.org \
    --to=jic23@kernel.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=fabio.estevam@freescale.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=knaack.h@gmx.de \
    --cc=kristina.martsenko@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=pmeerw@pmeerw.net \
    --cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).