All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald <pmeerw@pmeerw.net>
Subject: Re: [PATCH 0/6] fixes, cleanup and improvements for m62332
Date: Sat, 12 Sep 2015 11:13:37 +0100	[thread overview]
Message-ID: <55F3FAD1.1040703@kernel.org> (raw)
In-Reply-To: <CALT56yOWN5U5gcmGo=PfGBDUxMpNpVDhUYshF3B+KV39598Qqw@mail.gmail.com>

On 31/08/15 17:09, Dmitry Eremin-Solenikov wrote:
> Hello,
> 
> 2015-08-31 18:00 GMT+03:00 Jonathan Cameron <jic23@kernel.org>:
>> On 28/08/15 22:59, Hartmut Knaack wrote:
>>> A set of patches to address some issues I spotted during review.
>>>
>>> Hartmut Knaack (6):
>>>   iio:dac:m62332: share scale and offset
>>>   iio:dac:m62332: shutdown on remove
>>>   iio:dac:m62332: use ARRAY_SIZE
>>>   iio:dac:m62332: drop unrequired variable
>>>   iio:dac:m62332: address some style issues
>>>   iio:dac:m62332: use dynamic scale
>>>
>>>  drivers/iio/dac/m62332.c | 63 +++++++++++++++++++++++++-----------------------
>>>  1 file changed, 33 insertions(+), 30 deletions(-)
>>>
>> Other than letting this series sit on the list a few days longer,
>> for Dmitry or others to take a look at it, I'm happy with this series.
> 
> The changes look good, however I'd like to test them on my hardware first.
> 
Hi Dmitry,

Sorry I'd forgotten you sent this so have just backed out the first couple
for now.  Any idea when you might get a chance to test these out?  We
aren't in a rush given timing relative to the cycle, but always
good to have some idea of how long things are likely to take!

Thanks,

Jonathan

  reply	other threads:[~2015-09-12 10:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28 21:59 [PATCH 0/6] fixes, cleanup and improvements for m62332 Hartmut Knaack
2015-08-28 21:59 ` [PATCH 1/6] iio:dac:m62332: share scale and offset Hartmut Knaack
2015-08-31 14:53   ` Jonathan Cameron
2015-09-12 10:11     ` Jonathan Cameron
2015-09-12 10:14       ` Jonathan Cameron
2015-09-27 15:56         ` Jonathan Cameron
2015-10-11 14:40   ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 2/6] iio:dac:m62332: shutdown on remove Hartmut Knaack
2015-08-31 12:56   ` Daniel Baluta
2015-08-31 19:26     ` Hartmut Knaack
2015-10-11 14:42     ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 3/6] iio:dac:m62332: use ARRAY_SIZE Hartmut Knaack
2015-08-31 12:58   ` Daniel Baluta
2015-10-11 14:43     ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 4/6] iio:dac:m62332: drop unrequired variable Hartmut Knaack
2015-08-31 19:46   ` Daniel Baluta
2015-10-11 14:44     ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 5/6] iio:dac:m62332: address some style issues Hartmut Knaack
2015-10-11 14:45   ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 6/6] iio:dac:m62332: use dynamic scale Hartmut Knaack
2015-10-11 14:46   ` Jonathan Cameron
2015-08-31 15:00 ` [PATCH 0/6] fixes, cleanup and improvements for m62332 Jonathan Cameron
2015-08-31 16:09   ` Dmitry Eremin-Solenikov
2015-09-12 10:13     ` Jonathan Cameron [this message]
2015-10-03 11:16       ` Jonathan Cameron
2015-10-11 14:38         ` 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=55F3FAD1.1040703@kernel.org \
    --to=jic23@kernel.org \
    --cc=dbaryshkov@gmail.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.