Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1441301ybe; Thu, 5 Sep 2019 15:48:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqytgRXpTKe/buIIpYMrh+3LryZD7oBAvhs2oYhnim+g+vTKMN/YN4qgMSZeO/nPDordVsPP X-Received: by 2002:a62:198b:: with SMTP id 133mr4453824pfz.257.1567723715855; Thu, 05 Sep 2019 15:48:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567723715; cv=none; d=google.com; s=arc-20160816; b=kXJZs7GU7udXTuPz1lVhcyiYI/emagOSQXphwHHQAKr79yPOvWH34C0QJNKCnm4I16 97miqFqwTrIf7/gCHmY7+kfPQrvacO7Ym3HYUA8JOqUsh++yQXu9K4r2VBXUvWhd6jlS 64NLXZ+I71RdJ5GI25OW0Lk6Is3yesCn6R3wlX3YUEShcL2Pp4AkbfyEDtffrLYtarA+ bGSlBAaqRncHeCNliAIIZwthOfhW84TkqI2/vbSSaEnwG6hN9AmlhcldhMbeDQi+ECJj ueGLAkUv5fQzrsywP5c0UCDe1GM/eOd9ZiuOiz9QwnKXTRWF548U6lpMPqh2yR0+clTs xqCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=SnPGp9562UZ85Rk9x4JKmfzSUuZlqkHyZdsIAk5OOHA=; b=rTkSZ1n6TJmpljwV9EVO0EQcKLfifVtMBovQt9GtZBpotUMAapCygI/fzMSqwNxRrQ 1JVVdek9DnIXIPwaXFdR/l+uj7k8q3P0fxzdsb2Ur/ilRJpCm4NK+neErHM1BAuKvQAU DAxfWHLSNOXsYV+VOebZGozNJ+CP2sNukgo6Dnx9RZgImjZ0BV7FvcqqjDaZmD20GMkT fm0+D23cUPTxNcSs5se1d3xUCz2wwptCZL8i1R0Dn0GP2VMLEXFCBKJfBiKyts1Er3ee 8igFOZRc+V875AHPfLduPqF/WKHnnpRJMVBcicMKyxNV5W1LCm9ekSE+FT2Rc8BWw+Md pIDw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x14si3277955plm.44.2019.09.05.15.48.18; Thu, 05 Sep 2019 15:48:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389666AbfIETCh (ORCPT + 99 others); Thu, 5 Sep 2019 15:02:37 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:44071 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389519AbfIETCh (ORCPT ); Thu, 5 Sep 2019 15:02:37 -0400 Received: from p5de0b6c5.dip0.t-ipconnect.de ([93.224.182.197] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1i5x1U-0007f9-5T; Thu, 05 Sep 2019 21:02:24 +0200 Date: Thu, 5 Sep 2019 21:02:23 +0200 (CEST) From: Thomas Gleixner To: Mike Travis cc: Ingo Molnar , "H. Peter Anvin" , Andrew Morton , Borislav Petkov , Christoph Hellwig , Dimitri Sivanich , Russ Anderson , Hedi Berriche , Steve Wahl , x86@kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 0/8] x86/platform/UV: Update UV Hubless System Support In-Reply-To: <20190905184741.256857552@stormcage.eag.rdlabs.hpecorp.net> Message-ID: References: <20190905184741.256857552@stormcage.eag.rdlabs.hpecorp.net> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mike, On Thu, 5 Sep 2019, Mike Travis wrote: > These patches support upcoming UV systems that do not have a UV HUB. > > * Save OEM_ID from ACPI MADT probe > * Return UV Hubless System Type > * Add return code to UV BIOS Init function > * Setup UV functions for Hubless UV Systems > * Add UV Hubbed/Hubless Proc FS Files > * Decode UVsystab Info > * Account for UV Hubless in is_uvX_hub Ops Can you please in future mark the next version of a patch or patch series with [PATCH V2 n/M] so its clear that this is something different and also add a quick summary what changed vs. V1? Adding to each patch which changed a short change info _after_ the '---' discard line is also good practice and helps reviewers to figure out which part needs to be looked at. Thanks tglx