mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Zhang Rui <rui.zhang@intel.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Eduardo Valentin" <edubezval@gmail.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Lothar Waßmann" <LW@KARO-electronics.de>,
	"Dong Aisheng" <aisheng.dong@nxp.com>,
	"Bai Ping" <ping.bai@nxp.com>,
	"Anson Huang" <Anson.Huang@nxp.com>,
	"Octavian Purdila" <octavian.purdila@nxp.com>,
	"Fabio Estevam" <fabio.estevam@nxp.com>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Shawn Guo" <shawnguo@kernel.org>
Subject: Re: [PATCH v2 3/5] thermal: imx: Add support for reading OCOTP through nvmem
Date: Wed, 16 Aug 2017 18:33:41 +0300	[thread overview]
Message-ID: <1502897621.23210.41.camel@nxp.com> (raw)
In-Reply-To: <1502197100.4296.45.camel@intel.com>

On Tue, 2017-08-08 at 20:58 +0800, Zhang Rui wrote:
> On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote:
> > On 08/08/17 12:38, Leonard Crestez wrote:
> > > On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
> > > > On 08/08/17 08:21, Zhang Rui wrote:

> > > > > I'm okay with the thermal change.
> > > > > We still need ACK for the nvmem changes in this patch series.

> > > > NVMEM changes are already sent to Greg K H with other patches
> > > > https://lkml.org/lkml/2017/8/8/436, should appear in next.

> > > These patches have a compile-time dependency on each other.
> > > Wouldn't it make more sense for the whole series to go through a single
> > > maintainer tree, atomically? Most of the changes are in driver/thermal.

> > I was expecting that the nvmem change go in as fix in a rc release
> > so that you could apply the other patches after that.
> > 
> > Let me ping Greg about this!!

> As Shawn is okay with patch 4/5 and 5/5, I guess I can queue patch 1/5,
> 3/5, 4/5, 5/5 for 4.14-rc1, if the nvmem patch can catch 4.13, or I can
> queue the full patch set for 4.14, with Srinivas' ACK.

It's been a week since the last email and it seems that nothing
happened. I can't find any of these patches in either torvalds/master
or linux-next. It seems to me that the nvmem series linked above was
not picked up after all?

It's not clear how to proceed. It's been more a month since the series
was sent so maybe I should resend it but it's not clear who would pick
it up.

--
Regards,
Leonard

  reply	other threads:[~2017-08-16 15:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 14:11 [PATCH v2 0/5] thermal: imx: Add nvmem-cells binding on imx6sx Leonard Crestez
2017-07-14 14:11 ` [PATCH v2 1/5] thermal: imx: Add nvmem-cells alternate binding for OCOTP access Leonard Crestez
2017-07-17 18:57   ` Rob Herring
2017-07-14 14:11 ` [PATCH v2 2/5] nvmem: core: Add nvmem_cell_read_u32 Leonard Crestez
2017-07-25  8:07   ` Shawn Guo
2017-08-25  9:07   ` Srinivas Kandagatla
2017-08-28 10:51     ` Leonard Crestez
2017-07-14 14:11 ` [PATCH v2 3/5] thermal: imx: Add support for reading OCOTP through nvmem Leonard Crestez
2017-07-25  8:08   ` Shawn Guo
2017-08-08  7:21     ` Zhang Rui
2017-08-08 11:00       ` Srinivas Kandagatla
2017-08-08 11:38         ` Leonard Crestez
2017-08-08 11:44           ` Srinivas Kandagatla
2017-08-08 12:58             ` Zhang Rui
2017-08-16 15:33               ` Leonard Crestez [this message]
2017-08-25  2:20                 ` Zhang Rui
2017-07-14 14:11 ` [PATCH v2 4/5] ARM: dts: imx6sx: Use nvmem-cells for tempmon Leonard Crestez
2017-07-25  8:11   ` Shawn Guo
2017-10-18  2:29   ` Shawn Guo
2017-07-14 14:11 ` [PATCH v2 5/5] ARM: dts: imx6ul: Add imx6ul-tempmon Leonard Crestez
2017-07-17 14:00 ` [PATCH v2 0/5] thermal: imx: Add nvmem-cells binding on imx6sx Lothar Waßmann
2017-08-31  8:48 ` Shawn Guo
2017-08-31 13:11   ` Zhang Rui
2017-09-20  1:40     ` Zhang Rui

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=1502897621.23210.41.camel@nxp.com \
    --to=leonard.crestez@nxp.com \
    --cc=Anson.Huang@nxp.com \
    --cc=LW@KARO-electronics.de \
    --cc=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=octavian.purdila@nxp.com \
    --cc=ping.bai@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=shawnguo@kernel.org \
    --cc=srinivas.kandagatla@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome