mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Zhangjin Wu <falcon@tinylab.org>,
	thomas@t-8ch.de, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: nolibc patches, still possible for 6.5 ?
Date: Thu, 8 Jun 2023 09:37:34 -0700	[thread overview]
Message-ID: <c4b7c058-4c9f-4804-ba00-e7a9f2df4e3e@paulmck-laptop> (raw)
In-Reply-To: <ZIFZxLvMlUXxLGJE@1wt.eu>

On Thu, Jun 08, 2023 at 06:32:04AM +0200, Willy Tarreau wrote:
> 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!

And done!

							Thanx, Paul

  reply	other threads:[~2023-06-08 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 13:20 Willy Tarreau
2023-06-04 22:57 ` Paul E. McKenney
2023-06-05  3:26   ` Willy Tarreau
2023-06-07 21:03     ` Paul E. McKenney
2023-06-07 21:22       ` Willy Tarreau
2023-06-07 23:06         ` Paul E. McKenney
2023-06-08  4:32           ` Willy Tarreau
2023-06-08 16:37             ` Paul E. McKenney [this message]
2023-06-07 21:19   ` Willy Tarreau
2023-06-07 22:58     ` Paul E. McKenney
2023-06-08  4:36       ` Willy Tarreau
2023-06-08 16:39         ` Paul E. McKenney
2023-06-08  8:13     ` Zhangjin Wu
2023-06-08  8:21       ` Willy Tarreau
2023-06-08 16:40         ` Paul E. McKenney
2023-06-05 10:44 ` Thomas Weißschuh
2023-06-06  4:48   ` Willy Tarreau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c4b7c058-4c9f-4804-ba00-e7a9f2df4e3e@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=falcon@tinylab.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=thomas@t-8ch.de \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®