All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
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: Wed, 7 Jun 2023 23:22:54 +0200	[thread overview]
Message-ID: <ZID1LnvAj1lamHhv@1wt.eu> (raw)
In-Reply-To: <ec85bd36-9b39-458c-9618-af500656ca7b@paulmck-laptop>

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 :-/

Thanks,
Willy

  reply	other threads:[~2023-06-07 21:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 13:20 nolibc patches, still possible for 6.5 ? 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 [this message]
2023-06-07 23:06         ` Paul E. McKenney
2023-06-08  4:32           ` Willy Tarreau
2023-06-08 16:37             ` Paul E. McKenney
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=ZID1LnvAj1lamHhv@1wt.eu \
    --to=w@1wt.eu \
    --cc=falcon@tinylab.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=thomas@t-8ch.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.