Re: [PATCH v2 3/5] thermal: imx: Add support for reading OCOTP through nvmem
From: Zhang Rui
Date: Thu Aug 24 2017 - 22:20:45 EST
On Wed, 2017-08-16 at 18:33 +0300, Leonard Crestez wrote:
> 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!!
> >
Srinivas,
Will you take patch 2/5?
Only after that, we can push the other changes.
thanks,
rui
> > 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