All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Giuseppe Barba <giuseppe.barba@st.com>,
	Denis Ciocca <denis.ciocca@st.com>,
	Gregor Boirie <gregor.boirie@parrot.com>,
	Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: Re: [PATCH 1/2] iio: st_sensors: centralize I2C probe() code
Date: Sat, 19 Nov 2016 12:35:24 +0000	[thread overview]
Message-ID: <86e5d69d-0a92-bd2f-3c26-ccafe40d69e3@kernel.org> (raw)
In-Reply-To: <CACRpkdb7T3jm93AeTyg+c6to+8DStKw_DEC56_L9JAYcST8KpQ@mail.gmail.com>

On 14/11/16 12:25, Linus Walleij wrote:
> On Sat, Nov 12, 2016 at 5:11 PM, Jonathan Cameron <jic23@kernel.org> wrote:
> 
>> Also wondering why we ended up with the divide between generic
>> and specific where it was rather than as you have it here.
>> oh well.  Made sense at the time I guess ;)
> 
> This is not even all of it. There is still a bunch of code
> duplicated in all the subdrivers, but I'll try to collect it up
> and centralize it better.
Cool.

Feel free to bump this one if we don't here from Giuseppe or Denis over the next
week or so and I'll take a view on it as they are probably snowed under!

Jonathan
> 
> Yours,
> Linus Walleij
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2016-11-19 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 10:18 [PATCH 1/2] iio: st_sensors: centralize I2C probe() code Linus Walleij
2016-11-12 16:11 ` Jonathan Cameron
2016-11-14 12:25   ` Linus Walleij
2016-11-19 12:35     ` 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=86e5d69d-0a92-bd2f-3c26-ccafe40d69e3@kernel.org \
    --to=jic23@kernel.org \
    --cc=denis.ciocca@st.com \
    --cc=giuseppe.barba@st.com \
    --cc=gregor.boirie@parrot.com \
    --cc=leonard.crestez@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.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 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.