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 BFE56C77B7D for ; Mon, 15 May 2023 19:28:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244405AbjEOT2h (ORCPT ); Mon, 15 May 2023 15:28:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44094 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245097AbjEOT2g (ORCPT ); Mon, 15 May 2023 15:28:36 -0400 Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 69BC415268 for ; Mon, 15 May 2023 12:28:25 -0700 (PDT) Received: by mail-io1-xd2a.google.com with SMTP id ca18e2360f4ac-76c56d0e265so46093639f.0 for ; Mon, 15 May 2023 12:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1684178904; x=1686770904; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=lve7AMCKBIRfrjlxTp6FW8i8QEFQiCuhMHIDwhiIss8=; b=RF+zVb0BamcWpTMev05W2IxnT2uUFnYaRkZtDbxP75tzhFQvg5j57Eo5NSAhgD6Dvl TMPlpM6Ep8MOJ/u4+nBauqltl2HcPYrERCkVZ+/gB6ey0VquOtr+CoDmsckUn2OWCf4w 6gr35WY1uHzU1wIrgkPVCK0JOIQ044rlhbqGI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684178904; x=1686770904; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=lve7AMCKBIRfrjlxTp6FW8i8QEFQiCuhMHIDwhiIss8=; b=X4PYI7U8TgyGJwAUplmwz9M3LT7m9AWRA/O9m7p33vDwF59rdtdCIYzlmgQMucb3aF th4WX68mfcaZfW0q9+GGC3+Yao6bsLvuP0+r19ymh36UClg9LTpWmXQ0QpfnO5mc/oqo TGdiHT1g5li4lsRf31dzlvH3nx8oXF9XBgyB4FDs2qGMSNEZqcM1APptYYdBJt9awNYe Qc0AEJRnoRICq6PV78EAmxd8cGvLdTggJih4ecf8/v0VUTi3GT5GU6spJFgI97+2OccZ Gws44r1BlGliJeSujIRkRdHYwh2D59SBNGQ14hPFBNFCs0C6LSPs36ji5rXvLynigI+8 OFaA== X-Gm-Message-State: AC+VfDzFRG0JwynOfKcxYd5MaTqXd8Yy4vTenXb8Oj9snJYZMlDFDey6 c+m9bXsSLD3Oxlo8tvfwfwqJqw== X-Google-Smtp-Source: ACHHUZ4EDk8UcoxaPM0Gds09yHQNeM7fz29F3jhwT2XU2B2prmwPcovmsI+NsdcV8iVvKomYUzrWaQ== X-Received: by 2002:a92:a010:0:b0:32f:1232:f5d5 with SMTP id e16-20020a92a010000000b0032f1232f5d5mr392211ili.2.1684178904661; Mon, 15 May 2023 12:28:24 -0700 (PDT) Received: from [192.168.1.128] ([38.15.45.1]) by smtp.gmail.com with ESMTPSA id v13-20020a92c6cd000000b003358e4653c6sm4441930ilm.36.2023.05.15.12.28.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 May 2023 12:28:24 -0700 (PDT) Message-ID: <96c6fdf7-e589-ca56-9314-1d437b8082ac@linuxfoundation.org> Date: Mon, 15 May 2023 13:28:23 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: linux-next: duplicate patch in the rcu tree Content-Language: en-US To: paulmck@kernel.org, Stephen Rothwell Cc: Shuah Khan , Mark Brown , Linux Kernel Mailing List , Linux Next Mailing List , Shuah Khan References: <20230511090010.2916e9d7@canb.auug.org.au> <59c2fd36-6920-47d8-a79c-9ff3fcf7c7ae@paulmck-laptop> From: Shuah Khan In-Reply-To: <59c2fd36-6920-47d8-a79c-9ff3fcf7c7ae@paulmck-laptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On 5/11/23 10:52, Paul E. McKenney wrote: > On Thu, May 11, 2023 at 09:00:10AM +1000, Stephen Rothwell wrote: >> Hi all, >> >> The following commit is also in the kselftest-fixes tree as a different >> commit (but the same patch): >> >> 6d9ed63d8bc3 ("tools/nolibc: Fix build of stdio.h due to header ordering") >> >> This is commit >> >> d7eafa64a158 ("tools/nolibc: Fix build of stdio.h due to header ordering") >> >> in the kselftest-fixes tree. > > I can currently cleanly remove this commit from the rest of the nolibc > commits in -rcu. > > However, I might need to re-introduce it in some way or another, for > example, if there are dependencies on it by future nolibc patches. > (I expect another batch in a few days.) > > So how would you like to proceed? > Paul, I can drop this from linux-kselftest fixes if that is the easier path. Just let me know. thanks, -- Shuah