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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 74AC4EC875B for ; Thu, 7 Sep 2023 21:32:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240577AbjIGVcY (ORCPT ); Thu, 7 Sep 2023 17:32:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48058 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229754AbjIGVcX (ORCPT ); Thu, 7 Sep 2023 17:32:23 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 134031BE6 for ; Thu, 7 Sep 2023 14:32:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1694122333; x=1725658333; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=uOFHji2mp0FYCt27UDl4aADtHaHkYEgXUonNnF8B460=; b=PyVKVmhfPZy9UhFIjQI1z0kpdmv6QO/oiCWB6KLNGwfnEN04TUJkifBv T0tMmvIrcBX/ksgKil/eNP/cte9b+q3bc4MJkqubKwcCzaXbBHIBAO0KA yCByHrhKqSHGy5+Jb3d1/Ssv4z/06osx+bsiACBPdT1gLAKuI+T4ChdV4 mFzzzluk2dGqdy8a+Fz9/y90EjxYt2ciUlNB8nyjkV9FFKUmHlcsRdGoj +T9RHYWXUDENDuElh6tawncLZP2fMG30Nps3YAoBtmimKFMon/qKObnej g18IxyEgBV52Uko2nd1W5pKccgz1XYIjuzm89XyKK2Q0IU/Krb/ocEr3Y g==; X-IronPort-AV: E=McAfee;i="6600,9927,10826"; a="408474038" X-IronPort-AV: E=Sophos;i="6.02,236,1688454000"; d="scan'208";a="408474038" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Sep 2023 14:32:12 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10826"; a="771451547" X-IronPort-AV: E=Sophos;i="6.02,236,1688454000"; d="scan'208";a="771451547" Received: from ningle-mobl2.amr.corp.intel.com (HELO [10.209.13.77]) ([10.209.13.77]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Sep 2023 14:32:11 -0700 Message-ID: <81ee91fa-5546-4ca8-e8bc-765174938fc5@intel.com> Date: Thu, 7 Sep 2023 14:32:11 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Subject: Re: [PATCH] x86/platform/uv: Use alternate source for socket to node data Content-Language: en-US To: Steve Wahl Cc: Dimitri Sivanich , Russ Anderson , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , linux-kernel@vger.kernel.org References: <20230807141730.1117278-1-steve.wahl@hpe.com> <29cd0ee1-c638-9d8e-8a1c-8c2aa2e167e7@intel.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/7/23 14:25, Steve Wahl wrote: >> Does this need a stable@ tag when it gets applied? > I hadn't thought about that. I think it meets the requirements in > stable-kernel-rules.rst. And it looks like it should apply without > conflicts or prerequisites. So it probably should. Is there a way to > add a cc:stable tag at this point? I can do it when I apply it. I just wanted to make sure there wasn't a good reason you left off the cc:stable.