From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jae Hyun Yoo Subject: Re: [PATCH v2 1/8] [PATCH 1/8] drivers/peci: Add support for PECI bus driver core Date: Thu, 22 Feb 2018 09:20:47 -0800 Message-ID: <9bd825f4-8497-4e2a-b8ea-56888df754e7@linux.intel.com> References: <20180221161606.32247-1-jae.hyun.yoo@linux.intel.com> <20180221161606.32247-2-jae.hyun.yoo@linux.intel.com> <20180221175853.GA22320@kroah.com> <7f152459-a232-e62a-3c34-e995f8c85d63@linux.intel.com> <20180222065455.GA2428@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180222065455.GA2428@kroah.com> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Greg KH Cc: linux-hwmon@vger.kernel.org, andrew@lunn.ch, jdelvare@suse.com, arnd@arndb.de, linux-doc@vger.kernel.org, andrew@aj.id.au, benh@kernel.crashing.org, openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, joel@jms.id.au, linux@roeck-us.net, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org On 2/21/2018 10:54 PM, Greg KH wrote: > On Wed, Feb 21, 2018 at 12:42:30PM -0800, Jae Hyun Yoo wrote: >> On 2/21/2018 9:58 AM, Greg KH wrote: >>> On Wed, Feb 21, 2018 at 08:15:59AM -0800, Jae Hyun Yoo wrote: >>>> This commit adds driver implementation for PECI bus into linux >>>> driver framework. >>>> >>>> Signed-off-by: Jae Hyun Yoo >>>> --- >>> >>> Why is there no other Intel developers willing to review and sign off on >>> this patch? Please get their review first before asking us to do their >>> work for them :) >>> >>> thanks, >>> >>> greg k-h >>> >> >> Hi Greg, >> >> This patch set got our internal review process. Sorry if it's code quality >> is under your expectation but it's the reason why I'm asking you to review >> the code. Could you please share your time to review it? > > Nope. If no other Intel developer thinks it is good enough to put their > name on it as part of their review process, why should I? > > Again, please use the resources you have, to fix the obvious problems in > your code, BEFORE asking the community to do that work for you. > > greg k-h > Okay. I'll take our internal review process again on this patch set and collect more credit tags before submitting v3. Thanks for your advice! Jae