Message ID | 20221018094152.39787a20@canb.auug.org.au |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4ac7:0:0:0:0:0 with SMTP id y7csp1678260wrs; Mon, 17 Oct 2022 15:58:32 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6C4UeYkiL3SBmvdEZ0fGezBDANlyOkNwZ5KlOsk1cD3D1Jum7HSDgzR8rhvdlZCHRiMdC6 X-Received: by 2002:a05:6402:154c:b0:459:b29:da88 with SMTP id p12-20020a056402154c00b004590b29da88mr26922edx.296.1666047511873; Mon, 17 Oct 2022 15:58:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666047511; cv=none; d=google.com; s=arc-20160816; b=DYpfm7PtOZqgIyGGD0dq2iDA3fr5bj92xtWDZJ2WAttMffeHsstowTT2NgkyHOPzCh JPATvgOPnIZCMbF4+emm4zaZ0JdEYMNniRNW0zZQwS5nXtWNTrs6vzlpBCBnPhyNuyAT g2zp2NSnMfsu+DvOinWafFKAU+PmKRy/crMUlO8SQShJwOWOaUpnRfK/5NYxWt0FWAju FIkvzN6V9zw3ZcEugLLe3LBejleMjQCyMJ6Utr2F98N2OYtz6CJb+j5OE4HHPFuCo4/G wY5hBgShqd/v8gmTh7vsBL7OxJs3R/Z5jxDrEffAahWyVERKhtRwn2RItLIEM+zYVfML MqDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:subject:cc:to:from:date :dkim-signature; bh=Svfbpekr8l+cruikb0VblpuqiyFBzQGVTDIwB4rSlyg=; b=kvQx2i/r4CZ4mEXvYKU4tYVkZlp7zrbeHY7Y4RbrFWWB64JQteC1PjsFrbS0OirAQD YNXhN9QGZYJn/PQM2sYfFeE+tMRT2d/2abUP2ZmqmkMhCKSEiVina20Wuxu7zWt69fyS f3Cod/vAjsBScN10xKbad32DMwTsRBLnBbwjZ4C8ZL+1NzwXZoARkpS7K2wk8oO0qTzZ 1GQCSn2LW96uMcYU56khJIoM1gOMuCBiaO0d3U36l5K+TgjmUzoTZ7jSwd60fM2iRKRg J5x1P4AePAsdLHyTcZ0nB/IEd/jRr1iUjdTkjU7aC4cPRo0YggHzBd7WheoOxXEJBuKP omHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=pnzHY6cP; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v4-20020a056402348400b0045cfb639ff2si10177690edc.506.2022.10.17.15.58.04; Mon, 17 Oct 2022 15:58:31 -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; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=pnzHY6cP; 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 S230325AbiJQWl7 (ORCPT <rfc822;kernel.ruili@gmail.com> + 99 others); Mon, 17 Oct 2022 18:41:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57106 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230120AbiJQWl5 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 17 Oct 2022 18:41:57 -0400 Received: from gandalf.ozlabs.org (gandalf.ozlabs.org [150.107.74.76]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DF4A87C1DC; Mon, 17 Oct 2022 15:41:55 -0700 (PDT) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4MrsS15t9zz4x1G; Tue, 18 Oct 2022 09:41:53 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canb.auug.org.au; s=201702; t=1666046514; bh=Svfbpekr8l+cruikb0VblpuqiyFBzQGVTDIwB4rSlyg=; h=Date:From:To:Cc:Subject:From; b=pnzHY6cP+45a2ghSTqDlRwlruy11J9er28Ob1UVxSv9mL3Z/rSRgFcsKI55zLoVZa 56O3HsDy/MmeL4CRl/JwUyW/L9FL/Z7nfM0uHtobEMufkycOerJcyg/80TS9Tixui9 Mk2/YDDJeG7fo7q1nx4F6Sj2g2R3Y7OuJYj6THBku+GaP45neJs30ymqoZIAXoIxDR Fg12CJslzEwI+hXJyCblaFRb3AY3KEF+186JZPA/WwHkbH1gcqbyXgaqvzqvC7auRH pHAyF/yGIMHfHbfhy8Cd8yV5HEhmKPmba5URMeYeYMLZMAKBPoxIaB4U7MtO7pPLKw 1VZDlGEQfAW4g== Date: Tue, 18 Oct 2022 09:41:52 +1100 From: Stephen Rothwell <sfr@canb.auug.org.au> To: "Paul E. McKenney" <paulmck@kernel.org> Cc: Jianmin Lv <lvjianmin@loongson.cn>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux Next Mailing List <linux-next@vger.kernel.org>, "Rafael J. Wysocki" <rafael.j.wysocki@intel.com> Subject: linux-next: manual merge of the rcu tree with Linus' tree Message-ID: <20221018094152.39787a20@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/o8Kwt..5HbQ8hGw799583UI"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,SPF_PASS 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1746977435791911812?= X-GMAIL-MSGID: =?utf-8?q?1746977435791911812?= |
Series |
linux-next: manual merge of the rcu tree with Linus' tree
|
|
Commit Message
Stephen Rothwell
Oct. 17, 2022, 10:41 p.m. UTC
Hi all, Today's linux-next merge of the rcu tree got a conflict in: arch/loongarch/Kconfig between commit: c78c43fe7d42 ("LoongArch: Use acpi_arch_dma_setup() and remove ARCH_HAS_PHYS_TO_DMA") from Linus' tree and commit: 839fc1e464eb ("arch/loongarch: Add ARCH_HAS_NMI_SAFE_THIS_CPU_OPS Kconfig option") from the rcu 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.
Comments
On Tue, Oct 18, 2022 at 09:41:52AM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the rcu tree got a conflict in: > > arch/loongarch/Kconfig > > between commit: > > c78c43fe7d42 ("LoongArch: Use acpi_arch_dma_setup() and remove ARCH_HAS_PHYS_TO_DMA") > > from Linus' tree and commit: > > 839fc1e464eb ("arch/loongarch: Add ARCH_HAS_NMI_SAFE_THIS_CPU_OPS Kconfig option") > > from the rcu 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. Thank you, Stephen! For whatever it is worth, this will go away once I test my rebase to v6.1. Thanx, Paul > -- > Cheers, > Stephen Rothwell > > diff --cc arch/loongarch/Kconfig > index 903096bd87f8,c8864768dc4d..000000000000 > --- a/arch/loongarch/Kconfig > +++ b/arch/loongarch/Kconfig > @@@ -10,6 -10,8 +10,7 @@@ config LOONGARC > select ARCH_ENABLE_MEMORY_HOTPLUG > select ARCH_ENABLE_MEMORY_HOTREMOVE > select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI > + select ARCH_HAS_NMI_SAFE_THIS_CPU_OPS > - select ARCH_HAS_PHYS_TO_DMA > select ARCH_HAS_PTE_SPECIAL > select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST > select ARCH_INLINE_READ_LOCK if !PREEMPTION
diff --cc arch/loongarch/Kconfig index 903096bd87f8,c8864768dc4d..000000000000 --- a/arch/loongarch/Kconfig