From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail132-22.atl131.mandrillapp.com ([198.2.132.22]:39827 "EHLO mail132-22.atl131.mandrillapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752104AbcBYRDk (ORCPT ); Thu, 25 Feb 2016 12:03:40 -0500 Received: from pmta02.mandrill.prod.atl01.rsglab.com (127.0.0.1) by mail132-22.atl131.mandrillapp.com id hpspuo1sar8f for ; Thu, 25 Feb 2016 16:42:03 +0000 (envelope-from ) From: Greg KH Subject: Re: [PATCH 0/3] make efivarfs files immutable by default (for stable) To: Matt Fleming Cc: , Ard Biesheuvel , Peter Jones , Matthew Garrett , joeyli Message-Id: <20160225164158.GA22865@kroah.com> References: <1456417906-21471-1-git-send-email-matt@codeblueprint.co.uk> In-Reply-To: <1456417906-21471-1-git-send-email-matt@codeblueprint.co.uk> Date: Thu, 25 Feb 2016 16:42:03 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On Thu, Feb 25, 2016 at 04:31:43PM +0000, Matt Fleming wrote: > Stable folks, > > This is a backport of the efivarfs anti-bricking changes [1] for > stable. Some fixing up was required because the series doesn't > include the ucs2 cleanups that are in Linus' tree since they're not > really stable material. What stable tree(s) do you want these applied to? And if at all possible, I'd really prefer to take the original patches, additional things and all, for stable kernels, as 95%[1] of the time that we take "different" ones, there are bugs. It also makes things easier for us to take additional changes later on for other commits in the same area. So can we just take the originals please? thanks, greg k-h [1] Totally made up number, I think the true number is 100%, but maybe one or two patches have actually worked over the years. Most relevant example of this is some crypto patches that were "made simpler for stable" last week but were completely broken.