From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
Daniel Baluta <daniel.baluta@gmail.com>,
Peter Rosin <peda@lysator.liu.se>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Peter Rosin <peda@axentia.se>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/2] iio: mcp4531: Driver for Microchip digital potentiometers
Date: Mon, 28 Sep 2015 22:15:03 +0100 [thread overview]
Message-ID: <5609ADD7.3040509@kernel.org> (raw)
In-Reply-To: <A33F263C-A366-4ED3-AA62-F464C02F4232@jic23.retrosnub.co.uk>
On 28/09/15 10:01, Jonathan Cameron wrote:
>
>
> On 28 September 2015 09:11:09 BST, Daniel Baluta <daniel.baluta@gmail.com> wrote:
>
> On Mon, Sep 28, 2015 at 10:59 AM, Peter Rosin <peda@lysator.liu.se> wrote:
>
> On 2015-09-27 17:50, Jonathan Cameron wrote:
>
> On 23/09/15 15:26, Peter Rosin wrote:
>
> From: Peter Rosin <peda@axentia.se>
>
> Add support for Microchip digital potentiometers and rheostats
> MCP4531, MCP4532, MCP4551, MCP4552
> MCP4631, MCP4632, MCP4651, MCP4652
>
> DEVICE Wipers Steps Resistor Opts (kOhm) i2c address
> MCP4531 1 129 5, 10, 50, 100 010111x
> MCP4532 1 129 5, 10, 50, 100 01011xx
> MCP4551 1 257 5, 10 , 50, 100 010111x
> MCP4552 1 257 5, 10, 50, 100 01011xx
> MCP4631 2 129 5, 10, 50, 100 0101xxx
> MCP4632 2 129 5, 10, 50, 100 01011xx
> MCP4651 2 257 5, 10, 50, 100 0101xxx
> MCP4652 2 257 5, 10, 50, 100 01011xx
>
> Datasheet: http://www.microchip.com/downloads/en/DeviceDoc/22096b.pdf
>
> Applied to the togreg branch of iio.git - initially pushed out as
> testing for the autobuilders to play with it.
>
> If anyone wants to add reviewed-by / acked-by then as I'll be
> rebasing sometime in next few days anyway there is still time!
>
>
> Great, thanks,
>
> but I don't see this where I expected it[1]. So, the question is if I'm
> too impatient, if am I looking in the wrong place or if you perhaps forgot
> to actually push it out? Or if something went totally wrong and the patches
> got lost...
>
>
> Make sure you look for the testing branch. Also, do not worry about this.
>
> Sometimes, Jonathan pushes the patches locally to his setup and later
> syncs with the remote repo.
>
>
> What Daniel is politely saying is sometimes I forget to push them out!
> Oops. Machine is at home and powered down so should push testing branch this
> evening if I remember.
Should be there (in the testing branch) now.
J
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2015-09-28 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 14:26 [PATCH v6 0/2] Driver for Microchip digital potentiometers Peter Rosin
2015-09-23 14:26 ` [PATCH v6 1/2] iio: resistance: Document that resistance can be output Peter Rosin
2015-09-27 15:46 ` Jonathan Cameron
2015-09-23 14:26 ` [PATCH v6 2/2] iio: mcp4531: Driver for Microchip digital potentiometers Peter Rosin
2015-09-27 15:50 ` Jonathan Cameron
2015-09-28 7:59 ` Peter Rosin
2015-09-28 8:11 ` Daniel Baluta
2015-09-28 9:01 ` Jonathan Cameron
2015-09-28 21:15 ` 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=5609ADD7.3040509@kernel.org \
--to=jic23@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=peda@lysator.liu.se \
/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).