Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp531109rwr; Thu, 4 May 2023 06:35:02 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6TJ9n5FUWtT0Ts2aDvv5zGWrL0kHoo2wPRIRoGSMkDUsjtacQVXqR3dA61uprGsOiaL2+t X-Received: by 2002:a17:902:b097:b0:1ab:1301:6a70 with SMTP id p23-20020a170902b09700b001ab13016a70mr3984956plr.13.1683207302465; Thu, 04 May 2023 06:35:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683207302; cv=none; d=google.com; s=arc-20160816; b=tycTmSuLJn0PCwoYQ4XGtQ1VdM8uELWHqGRjh7SHK9AWiBg5kL4t0MCospoVm7Pust JM0+ChrXAnRIpxZSB6FyyF40xDxvSM3nqiqjFTheJ1480W8UFj+cuDV0KqHmTrO04O3N dFJ8SI4rkvm1dvJAAlbyD9iPhopxj5NYOqbQ0C0TlLVgkwCHVtkcs/vMnfbu+4iQ55W7 YdFR4GFkD8FayC1hgH3BgXHfClUhZKCD9YOFGkpGQoHFm4qtazu++PN+MRQVB9GLUXPV cIFgZT6yNX5MDxibg9chrTatxB7DGAtxrMLUJYPGJLCLlaC00jaE0fZiZ0qdagtaTohw UNzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=DRpqaf/3VkCdQzpR0HZkuKmX6rhq+FcXxWkNXtsWr54=; b=ekdoJmDTuPzKARs3HH2es2FINbJxdE3QEkCgYM8itbCRafg3mEEB6z3A+M/4o5tOLS DTLogdf+dl5xQVMj8Cmai7/+/v0RDxcA9WJQOL5+vPlQ94MTVuAtrmDVCNAQuR6VcZSG h4UhxdBtnVciNkONyyGRFGNIc3ey81DyClOWIoQIZejBpIQvEWMj6TtWYGkb2IBA1KAu XCrunb8SgyWvEtRS2xtVMJqlwWVoEGQbpWW68nxZdl5nJOQKm7N9arfaDyRKfYcqg/MP zMzmaJdWJMRDu4A4sOI+SQwB/L8CXraBJXX11WLL5haxaQGrbeJM+DPg0phhifxnylxw Hwww== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c2-20020a17090a8d0200b0024dfb95d54csi9813280pjo.177.2023.05.04.06.34.47; Thu, 04 May 2023 06:35:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231143AbjEDNSr (ORCPT + 99 others); Thu, 4 May 2023 09:18:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52408 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231149AbjEDNSq (ORCPT ); Thu, 4 May 2023 09:18:46 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 15B077DA7; Thu, 4 May 2023 06:18:28 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 5C7396341A; Thu, 4 May 2023 13:18:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 51E81C4339B; Thu, 4 May 2023 13:18:27 +0000 (UTC) From: Mark Brown To: Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Peter Zijlstra Cc: Andrew Morton , Dave Hansen , Linux Kernel Mailing List , Linux Next Mailing List , Nhat Pham , Rick Edgecombe Subject: linux-next: manual merge of the tip tree with the origin tree Date: Thu, 4 May 2023 22:18:24 +0900 Message-Id: <20230504131824.182744-1-broonie@finisterre.sirena.org.uk> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIM_ADSP_NXDOMAIN, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/x86/entry/syscalls/syscall_64.tbl between commit: 5c289a59b1d08 ("cachestat: implement cachestat syscall") from the origin tree and commit: a9d48cbbcc40b ("x86/shstk: Introduce map_shadow_stack syscall") from the tip tree. I fixed it up (see below) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. diff --cc arch/x86/entry/syscalls/syscall_64.tbl index 227538b0ce801,f65c671ce3b14..0000000000000 --- a/arch/x86/entry/syscalls/syscall_64.tbl +++ b/arch/x86/entry/syscalls/syscall_64.tbl @@@ -372,7 -372,7 +372,8 @@@ 448 common process_mrelease sys_process_mrelease 449 common futex_waitv sys_futex_waitv 450 common set_mempolicy_home_node sys_set_mempolicy_home_node -451 64 map_shadow_stack sys_map_shadow_stack +451 common cachestat sys_cachestat ++452 64 map_shadow_stack sys_map_shadow_stack # # Due to a historical design error, certain syscalls are numbered differently