[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1515703795.31850.45.camel@kernel.crashing.org>
Date: Fri, 12 Jan 2018 07:49:55 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-hwmon@...r.kernel.org, devicetree@...r.kernel.org,
Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com>,
jdelvare@...e.com, arnd@...db.de, linux-doc@...r.kernel.org,
andrew@...id.au, openbmc@...ts.ozlabs.org,
linux-kernel@...r.kernel.org,
Jae Hyun Yoo <jae.hyun.yoo@...el.com>, linux@...ck-us.net,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon
drivers
On Thu, 2018-01-11 at 10:59 +0100, Greg KH wrote:
> And, if you use it in a device, it's still totally unsupported and
> insecure. Seriously, does no one actually pay attention to the patches
> I merge in the stable trees anymore?
Yeah not sure why we aren't picking an LTC here, it could be that it's
just a dev branch, not release, Joel, what's the process in that case ?
For anything going into products, if we're going to maintain a non-
upstream branch, we should definitely stick it to an LTS release or
we'll be missing a ton of security fixes.
Cheers,
Ben.
Powered by blists - more mailing lists