Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp1274943rwi; Wed, 26 Oct 2022 13:07:15 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4NwdU6RDDDniJ/Zj/5qafOKWFHTZvs4nog5xrC8Zk0rdRIKbVVLDwe9LHhgMxYA+2mXHjQ X-Received: by 2002:a65:6cce:0:b0:439:49b5:48b8 with SMTP id g14-20020a656cce000000b0043949b548b8mr39101595pgw.514.1666814824784; Wed, 26 Oct 2022 13:07:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666814824; cv=none; d=google.com; s=arc-20160816; b=oifqyPuEzHN+mTW5m8KMJa38DQtS8vOahA5e5tMelKm+77GlEjOIzk6RyUhGhazFMF bkJi5IehyMMPDrXRtBjDVZSy49kX+QZY5B3lhfGuROF6eiQTKOlAlwwrBExzxifJ3L7f k/onnUQ3hXP+JAwwShPwAGsB/4OzQCp9JnriHNEt2wCmtTxC73dx9uyfToEp6DaUvSel opnXpGhS5vAHWTjzlOewL5SxSedekMHm92WB6Bi5RRgaNa9YGzYy79rhvukiOXD2Hbd3 fR5JxgrdsOCKtnciaaSZtjrFTpu3MlCgINkvwN+Ig8y0h95+8U+Uqo/7gqujZXScId4z Ud5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=8rvn7vwx2ZjV+TKPPpahVm1H/vKOQHHAT7PXj71Ckn4=; b=tce+tz61eY2meef8tOqmqqoAi7OHCFRwWSeHEh0haTI5JKijjH5+gOkDiJSthJukha eSaaZBQVf0CMamfEsePGnYVTY8ow20PVmKdJs8TDwngIkZRHtosAMSnTRmi1WaCG86Zr /h23NN/S5+Xn/EHYYL0dFn5m0QDjiFurR/mXxyirgI8ITUx0gKs2EPP00A1iWuwr7odo /lM9Gxld+6C3+6wX9NYugkt1vKssKLusS//DVEji1JN/FHtCJpdnnE0jqulNFl0n5Jff SnwrJt3P7nqM3mAG0E3nwA53oW+Pn2VCbU27pHfUeG9gQvYBxaOZK6Q5YknXYUZ9csO2 9Y5g== 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 b4-20020a170903228400b0018678dab05dsi10092524plh.199.2022.10.26.13.06.46; Wed, 26 Oct 2022 13:07:04 -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 S233935AbiJZT7O (ORCPT + 99 others); Wed, 26 Oct 2022 15:59:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49236 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234650AbiJZT7J (ORCPT ); Wed, 26 Oct 2022 15:59:09 -0400 Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 7A0D53B98C; Wed, 26 Oct 2022 12:59:08 -0700 (PDT) Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 29QJx2xa024285; Wed, 26 Oct 2022 21:59:02 +0200 Date: Wed, 26 Oct 2022 21:59:02 +0200 From: Willy Tarreau To: "Paul E. McKenney" Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] selftests/nolibc: always rebuild the sysroot when running a test Message-ID: <20221026195902.GB24197@1wt.eu> References: <20221026054508.19634-1-w@1wt.eu> <20221026164825.GN5600@paulmck-ThinkPad-P17-Gen-1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221026164825.GN5600@paulmck-ThinkPad-P17-Gen-1> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 26, 2022 at 09:48:25AM -0700, Paul E. McKenney wrote: > On Wed, Oct 26, 2022 at 07:45:08AM +0200, Willy Tarreau wrote: > Works like a champ with reverting and unreverting c9388e0c1c6c > ("tools/nolibc/string: Fix memcmp() implementation"), thank you!!! Thanks for the feedback, and glad it suits your needs as well. I hope that it will progressively encourage a few of us to enhance it with more tests. > I have queued this. I expect to push this into the next merge window, > thus avoiding the need to document the need for "make clean" in my > pull request. ;-) Stupid question, is it really worth postponing it, considering that we've just introduced this series right now ? I mean, if the current usage is confusing, it's probably better to propose the fix before 6.1-final ? It's not a new feature here but rather a fix for a recently introduced one, thus I think it could be part of the next fix series. Rest assured I don't want to put a mess into your patch workflow, just asking :-) Thanks! Willy