From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F1B71C2BCA1 for ; Fri, 7 Jun 2019 16:59:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C8E042089E for ; Fri, 7 Jun 2019 16:59:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="aCgMbb81" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728736AbfFGQ7E (ORCPT ); Fri, 7 Jun 2019 12:59:04 -0400 Received: from mail.skyhub.de ([5.9.137.197]:33200 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729241AbfFGQ7E (ORCPT ); Fri, 7 Jun 2019 12:59:04 -0400 Received: from zn.tnic (p200300EC2F066300951FA2F4E0AD5C5F.dip0.t-ipconnect.de [IPv6:2003:ec:2f06:6300:951f:a2f4:e0ad:5c5f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 21F031EC0985; Fri, 7 Jun 2019 18:59:02 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1559926742; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=/2NcNch3R68K7lUglKrZM9JHVa8TdBrm5yFg3WS60WU=; b=aCgMbb81ahA64+mVjl7lpndBl9sa9MEar0rZrGyE1RXeMA5E+WwIyLmP2YNeZq455HoxKU CqIf23HRuoqO+2J44ElTft1ANGYOUQwQA/GuKENfqTZtLiu1nr/hRKE3w5t/mGvdSfGbh6 mE1eAdp36Y4+CkAVjmD5SeaQLX43/ho= Date: Fri, 7 Jun 2019 18:59:02 +0200 From: Borislav Petkov To: "Ghannam, Yazen" Cc: "Luck, Tony" , "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "x86@kernel.org" Subject: Re: [PATCH v3 5/6] x86/MCE: Save MCA control bits that get set in hardware Message-ID: <20190607165902.GJ20269@zn.tnic> References: <20190517174817.GG13482@zn.tnic> <20190517180607.GA21710@agluck-desk> <20190517193431.GI13482@zn.tnic> <20190517200225.GK13482@zn.tnic> <20190527232849.GC8209@cz.tnic> <20190607163723.GG20269@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-edac-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-edac@vger.kernel.org On Fri, Jun 07, 2019 at 04:44:24PM +0000, Ghannam, Yazen wrote: > I have another version of this set that I can send today. It includes > the changes for this patch and also includes the fix for the locking > bug message. > > Should I send out the new version? Or do you want me to wait for any > fixes on top of the current version? I don't understand - I think we said to feel free to rework it all by using https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=rc0%2b3-ras and reworking the whole branch to accomodate the changes and then sending a whole new series... -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.