Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752184AbeAJTRE (ORCPT + 1 other); Wed, 10 Jan 2018 14:17:04 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:44966 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750861AbeAJTRC (ORCPT ); Wed, 10 Jan 2018 14:17:02 -0500 Date: Wed, 10 Jan 2018 20:17:03 +0100 From: Greg KH To: Jae Hyun Yoo Cc: joel@jms.id.au, andrew@aj.id.au, arnd@arndb.de, jdelvare@suse.com, linux@roeck-us.net, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org, linux-arm-kernel@lists.infradead.org, openbmc@lists.ozlabs.org, Jae Hyun Yoo Subject: Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers Message-ID: <20180110191703.GA20248@kroah.com> References: <20180109223126.13093-1-jae.hyun.yoo@linux.intel.com> <20180110101755.GA5822@kroah.com> <006c4a95-9299-bd17-6dec-52578e8461ae@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <006c4a95-9299-bd17-6dec-52578e8461ae@linux.intel.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Wed, Jan 10, 2018 at 11:14:34AM -0800, Jae Hyun Yoo wrote: > On 1/10/2018 2:17 AM, Greg KH wrote: > > On Tue, Jan 09, 2018 at 02:31:20PM -0800, Jae Hyun Yoo wrote: > > > From: Jae Hyun Yoo > > > > > > Hello, > > > > > > This patch set provides support for PECI of AST2400/2500 which can give us PECI > > > functionalities such as temperature monitoring, platform manageability, > > > processor diagnostics and failure analysis. Also provides generic peci.h and > > > peci_ioctl.h headers to provide compatibility to peci drivers that can be > > > implemented later e.g. Nuvoton's BMC SoC family. > > > > What is the "dev-4.10" in the subject for? 4.10 is really old and > > obsolete :( > > > > thanks, > > > > greg k-h > > > > I made this patch set on top of the v4.10 which OpenBmc project is currently > using. I'll rebase this patch set onto the current kernel.org mainline. What is "OpenBmc", and why are they using an obsolete and insecure kernel for their project? That seems like a very foolish thing to do... thanks, greg k-h