Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp167619rwd; Wed, 7 Jun 2023 21:45:39 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4Bd+HqKgBcHmneDy2EFG4H1AuDlpcf0U0iPsUqiUpQCdtNxNHLWMCou+0IC/XdjDmFNVZ4 X-Received: by 2002:a05:6358:611a:b0:129:cbc5:95ca with SMTP id 26-20020a056358611a00b00129cbc595camr1883263rws.16.1686199539052; Wed, 07 Jun 2023 21:45:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686199539; cv=none; d=google.com; s=arc-20160816; b=T/XrBRk7phucp5J9QbL/7kq3GKJO+5U5hI/vrIOw7MmKg/IkPHI5JIIOiRT4KUUdbq TKhAs59NzXOFtDR+EHQ1yU/Ypprv/w79fhWfhQR6/GVxA87TfpjTbpgaqclP9a+L7WMo 5n7wawA0CYiovWp71S/ic9V5jfDpCKLWb69/5OmmLQlY3sZeYLcJJWvtj6xNmduv3xON zGblU/Qh00q58EoBx9y32DqBX+jIB4jkjK2Wbt7Aqr0eeJWn78SFr1/FobbGQDBtIaCt KtGxZK/h9Ylhh3KuO4F7yb6ZLFkNRCELozUNzvQoDk9jdodb8J10MgLmveqv++7cS8/7 aZ8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=V7zMUrAMJKq/Xs/eXCsLWs2hGdxl2S5jqsMBSKXDfL8=; b=yN6wbYQFXMr3VVEDZO1u/iNWiz3FmSk7EaVrSOf7Zci7QeiXvzahCg4QQZK6XtIyTs UeyBj9FAJBNUFYEZhOhx4wrnohQCUi1ceELq6AOKO9bLBC7t/JSKF4Squfo9ZocsGhV2 E/L0SC2eV53u17fbN3v08F+/g8fy7BBefBVDskjc+cjDFgTdPp9VVxqI7BfaabFGZtk2 DhDFr/jlF4cmr07rflKwVhkn8K5GahJgmXuUV1Y+6NIBNqQGwhxAl3xDfQmB0JV3TYx9 AyyqaMxYdiyiK6CHE36XkKcQFxHTNftji1sIb6Juc7K7+7KvHKPzfYOsir3j8IGxeMD1 OLqQ== 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 z72-20020a63334b000000b00543cc95d776si359266pgz.660.2023.06.07.21.45.24; Wed, 07 Jun 2023 21:45:39 -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 S233802AbjFHEcU (ORCPT + 99 others); Thu, 8 Jun 2023 00:32:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232805AbjFHEcS (ORCPT ); Thu, 8 Jun 2023 00:32:18 -0400 Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 1416D83; Wed, 7 Jun 2023 21:32:15 -0700 (PDT) Received: (from willy@localhost) by mail.home.local (8.17.1/8.17.1/Submit) id 3584W4FQ015692; Thu, 8 Jun 2023 06:32:04 +0200 Date: Thu, 8 Jun 2023 06:32:04 +0200 From: Willy Tarreau To: "Paul E. McKenney" Cc: Zhangjin Wu , thomas@t-8ch.de, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org Subject: Re: nolibc patches, still possible for 6.5 ? Message-ID: References: <5494ac68-b4b9-434f-92c1-7e197c92a4ab@paulmck-laptop> <208b317e-8553-4d0d-b97c-a0e808fe98f2@paulmck-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <208b317e-8553-4d0d-b97c-a0e808fe98f2@paulmck-laptop> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, 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 On Wed, Jun 07, 2023 at 04:06:37PM -0700, Paul E. McKenney wrote: > On Wed, Jun 07, 2023 at 11:22:54PM +0200, Willy Tarreau wrote: > > On Wed, Jun 07, 2023 at 02:03:17PM -0700, Paul E. McKenney wrote: > > > > > (There were some kernel test > > > > > robot complaints as well, valid or not I am not sure.) > > > > > > > > You mean in relation with nolibc stuff (or nolibc-test) or something > > > > totally different ? > > > > > > Apologies, this was me being confused and failing to look closely. > > > > > > The complaints were not about nolibc, but rather about my patches that > > > they were on top of. Not your problem! > > > > Ah no problem :-) > > > > > And please let me know when the next batch from your tree are ready to go. > > > (You might have been saying that they were in your recent emails, but > > > I thought I should double-check.) > > > > No pb, I just sent it while you were writing and our emails have crossed :-) > > > > In short, it's ready now with branch 20230606-nolibc-rv32+stkp7a but if you > > need any more info (more detailed summary, a public repost of the whole > > series etc), just let me know. And I faced 2 kernel build errors on s390x > > and riscv about rcu_task something, though you might be interested :-/ > > And I pulled them in and got this from "make run": > > 138 test(s) passed, 0 skipped, 0 failed.[ 2.416045] reboot: Power down > > And this from "make run-user": > > 136 test(s) passed, 2 skipped, 0 failed. See all results in /home/git/linux-rcu/tools/testing/selftests/nolibc/run.out > > And run.out looks as it has before, so all looks good at this end. > > Thus, unless you tell me otherwise, I will move these to my nolibc branch > for the upcoming merge window. Perfect, thank you very much Paul! Willy