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 06E83C7EE23 for ; Thu, 8 Jun 2023 04:32:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233847AbjFHEcV (ORCPT ); Thu, 8 Jun 2023 00:32:21 -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> 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