linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	Olof Johansson <olof@lixom.net>, Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Guenter Roeck <groeck@chromium.org>,
	Gwendal Grignou <gwendal@chromium.org>
Subject: Re: [PATCH v4 0/4] Add support for cros-ec-sensors
Date: Thu, 1 Sep 2016 08:24:04 +0100	[thread overview]
Message-ID: <20160901072404.GD4921@dell> (raw)
In-Reply-To: <a911916d-05bc-6bcd-0aea-bfd7a3d4ff1b@kernel.org>

> >>>>> Given this dependency I'm assuming the best route for these is via
> >>>>> the MFD tree...
> >>>>>
> >>>>> Lee, shout if you want them to go a different route.
> >>>>
> >>>> IIO looks like a more suitable route.  Please provide me with a
> >>>> pull-request base off of an immutable tag.
> >>> Hi Lee,
> >>>
> >>> As far as I can tell the precursor patch above hasn't gone in your
> >>> tree yet which leaves me unable to take this through IIO for now.
> >>>
> >>> Maybe I'm missing something!
> >>>
> >>> Jonathan
> >>
> >> Hi Lee,
> >>
> >> Any movement on the dependency above?
> >>
> >> Last I can find was you adding your ack to it:
> >> [PATCH v2 1/2] mfd: cros_ec: Add MKBP event support
> >>
> >> https://lkml.org/lkml/2016/8/16/423
> > 
> > Well that's annoying.  Okay, well when I send out the pull-request for
> > this one, I will include you.
> > 
> > Actually, better still -- take all of them on one branch and I will
> > pull from you.  Saves the toing and froing.
> > 
> Sure. Will probably be the weekend before I get this sorted.

No rush.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2016-09-01  7:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01  9:54 [PATCH v4 0/4] Add support for cros-ec-sensors Enric Balletbo i Serra
2016-08-01  9:54 ` [PATCH v4 1/4] iio: cros_ec_sensors_core: Add common functions for the ChromeOS EC Sensor Hub Enric Balletbo i Serra
2016-08-01 16:57   ` Guenter Roeck
2016-08-15 15:28   ` Jonathan Cameron
2016-09-03 17:07     ` Jonathan Cameron
2016-10-25 17:12       ` Jonathan Cameron
2016-08-01  9:54 ` [PATCH v4 2/4] iio: cros_ec_sensors: add ChromeOS EC Contiguous Sensors driver Enric Balletbo i Serra
2016-08-15 15:28   ` Jonathan Cameron
2016-09-03 17:12     ` Jonathan Cameron
2016-10-25 17:12       ` Jonathan Cameron
2016-08-01  9:54 ` [PATCH v4 3/4] platform/chrome: Introduce a new function to check EC features Enric Balletbo i Serra
2016-08-09 13:59   ` Lee Jones
2016-10-25 17:14     ` Jonathan Cameron
2016-08-01  9:54 ` [PATCH v4 4/4] platform/chrome: cros_ec_dev - Register cros-ec sensors Enric Balletbo i Serra
2016-08-15 15:31   ` Jonathan Cameron
2016-09-03 17:20     ` Jonathan Cameron
2016-10-25 17:27       ` Jonathan Cameron
2016-08-15 15:24 ` [PATCH v4 0/4] Add support for cros-ec-sensors Jonathan Cameron
2016-08-16 12:49   ` Lee Jones
2016-08-21 19:57     ` Jonathan Cameron
2016-08-29 15:14       ` Jonathan Cameron
2016-08-30  8:57         ` Lee Jones
2016-08-31 20:06           ` Jonathan Cameron
2016-09-01  7:24             ` Lee Jones [this message]
2016-09-03 17:21               ` Jonathan Cameron
2016-10-18  8:35                 ` Enric Balletbo Serra
2016-10-18  8:56                   ` Jonathan Cameron
2016-10-22 17:49                     ` Olof Johansson
2016-10-22 18:47 ` 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=20160901072404.GD4921@dell \
    --to=lee.jones@linaro.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --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 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).