linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org,
	Vincent Pelletier <plr.vincent@gmail.com>,
	Tomasz Duszynski <tduszyns@gmail.com>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH v2] iio: adc: intel_mrfld_adc: Add Basin Cove ADC driver
Date: Tue, 3 Sep 2019 18:51:19 +0100	[thread overview]
Message-ID: <20190903185119.2328cf86@archlinux> (raw)
In-Reply-To: <20190902131301.GI2680@smile.fi.intel.com>

On Mon, 2 Sep 2019 16:13:01 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> On Sat, Mar 30, 2019 at 03:31:40PM +0000, Jonathan Cameron wrote:
> > On Tue, 26 Mar 2019 16:51:38 +0200
> > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >   
> > > From: Vincent Pelletier <plr.vincent@gmail.com>
> > > 
> > > Exposes the ADC device present on, at least, Intel Merrifield platform.
> > > 
> > > Based on work done by:
> > >   Yang Bin <bin.yang@intel.com>
> > >   Huiquan Zhong <huiquan.zhong@intel.com>
> > >   Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
> > >   Pavan Kumar S <pavan.kumar.s@intel.com>
> > > 
> > > Though it has been heavily rewritten for upstream.
> > > 
> > > Signed-off-by: Vincent Pelletier <plr.vincent@gmail.com>
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>  
> > 
> > Hmm. There is a very small ordering issue in probe vs remove, which
> > I'll probably just fix up.
> > 
> > However I don't yet have the header in my upstream so will wait
> > until that is there before applying.  If Lee or whoever is dealing
> > with that patch set puts out an immutable branch with it in then
> > let me know.
> > 
> > Give me a poke if I seem to have forgotten it.  
> 
> Hi, Jonathan.
> 
> Lee applied the main driver to his tree [1].
> Should I do anything for this one or is it applicable clean?
> 
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/commit/?id=b9a801dfa591
> 
Hmm. It's very late in the cycle and Lee doesn't have that in an immutable
branch (presumably because it's very late or it wasn't clear there was
a need to do so).  In theory I've done my last pull request to Greg
(though I messed it up so that's not quite true).

Will have to pick this up towards the start of the next cycle now I think.

Sorry, sometimes timing is against us!

Jonathan



  reply	other threads:[~2019-09-03 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 14:51 [PATCH v2] iio: adc: intel_mrfld_adc: Add Basin Cove ADC driver Andy Shevchenko
2019-03-30 15:31 ` Jonathan Cameron
2019-09-02 13:13   ` Andy Shevchenko
2019-09-03 17:51     ` Jonathan Cameron [this message]
2019-10-01  8:19       ` Andy Shevchenko
2019-10-15 15:14         ` Andy Shevchenko
2019-10-15 15:40           ` jic23
2019-10-15 20:05             ` 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=20190903185119.2328cf86@archlinux \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=plr.vincent@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=tduszyns@gmail.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).