Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754173AbcC0IcO (ORCPT ); Sun, 27 Mar 2016 04:32:14 -0400 Received: from mail.skyhub.de ([78.46.96.112]:48103 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751753AbcC0IcH (ORCPT ); Sun, 27 Mar 2016 04:32:07 -0400 Date: Sun, 27 Mar 2016 10:31:59 +0200 From: Borislav Petkov To: Henrique de Moraes Holschuh Cc: LKML , X86 ML Subject: Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels Message-ID: <20160327083159.GA32241@pd.tnic> References: <1435781656-1890-1-git-send-email-bp@alien8.de> <20160326233157.GA11398@khazad-dum.debian.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160326233157.GA11398@khazad-dum.debian.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 552 Lines: 16 On Sat, Mar 26, 2016 at 08:31:57PM -0300, Henrique de Moraes Holschuh wrote: > This patchset looks like it is pretty much a requirement for any distro that > ships AMD microcode updates... Maybe the two commits should be sent to > -stable, now that they have seen lots of testing in mainline 4.4.x as well > as SuSE kernels? I wouldn't say lots... :) Do you have any specific bug report(s) or similar in mind? Or is it more of a "it would be wise to backport" sentiment? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.