From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754391AbdHYCUk (ORCPT ); Thu, 24 Aug 2017 22:20:40 -0400 Received: from mga09.intel.com ([134.134.136.24]:43518 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754216AbdHYCUi (ORCPT ); Thu, 24 Aug 2017 22:20:38 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,423,1498546800"; d="scan'208";a="141803040" Message-ID: <1503627649.2774.6.camel@intel.com> Subject: Re: [PATCH v2 3/5] thermal: imx: Add support for reading OCOTP through nvmem From: Zhang Rui To: Leonard Crestez , Srinivas Kandagatla , Greg Kroah-Hartman Cc: Rob Herring , Eduardo Valentin , Mark Rutland , Lothar =?ISO-8859-1?Q?Wa=DFmann?= , Dong Aisheng , Bai Ping , Anson Huang , Octavian Purdila , Fabio Estevam , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Shawn Guo Date: Fri, 25 Aug 2017 10:20:49 +0800 In-Reply-To: <1502897621.23210.41.camel@nxp.com> References: <20170725080835.GD20064@dragon> <1502176915.4296.1.camel@intel.com> <26407dd5-a9b1-67c0-c4ab-d97fa0b88b79@linaro.org> <1502192287.24350.9.camel@nxp.com> <9732c524-fbdc-d1be-cd03-089dbb2266c4@linaro.org> <1502197100.4296.45.camel@intel.com> <1502897621.23210.41.camel@nxp.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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