From: Willy Tarreau <[email protected]>
To: Zhangjin Wu <[email protected]>
Cc: [email protected], [email protected], [email protected]
Subject: Re: [PATCH nolibc 0/19] Updates to nolibc for v6.7 (and three for v6.6)
Date: Fri, 27 Oct 2023 10:21:25 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
[CCed Thomas]
Hi Zhangjin,
On Fri, Oct 27, 2023 at 02:09:17AM +0800, Zhangjin Wu wrote:
> [out-of-tree]
>
> [ Sorry, please ignore the last one with lwt.eu, it should be 1wt.eu, seems a typo:
> https://lore.kernel.org/lkml/b34ce3cf-3fcc-4eb0-a658-229c197455ef@paulmck-laptop/ ]
Ah, indeed!
> Hi, Paul, Thomas and Willy
>
> I just learned our nolibc tree has been moved to another git repo and
> have seen this PR series. I was waiting for a new branch in Willy's repo ;-)
Yes, we also updated the MAINTAINERS file with it, now that the nolibc
family grows :-) I'll eventually remove my repo.
> Just a question: seems some patches of mine have been queued to Willy's
> local repo, but I haven't seen in this PR, I can't remember which ones
> are queued exactly, here may be at least one of them:
>
> https://lore.kernel.org/linux-kselftest/[email protected]/
Which one do you mean ? The one I'm seeing there in the discussion
mentions patch 3 ("use HOSTCC instead of CC") and I find it merged
already (commit 418c84682).
> Or do I need to send a new series for them? some of the commit message issues
> have been changed by Willy manually, so, that series online can not be merged
> simply, If necessary, I'm ok to resend them.
It's possible that something fell through the cracks, I've had a very
difficult experience of the many parallel discussion threads in the past,
but I can't guess what you find missing, so please be more specific about
these (or possibly resend them if you want), I'd just prefer to avoid
re-reviewing something already reviewed.
Thanks!
Willy
next prev parent reply other threads:[~2023-10-27 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 18:09 [PATCH nolibc 0/19] Updates to nolibc for v6.7 (and three for v6.6) Zhangjin Wu
2023-10-27 8:21 ` Willy Tarreau [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-26 18:05 Zhangjin Wu
2023-10-27 2:16 ` Paul E. McKenney
2023-10-12 19:32 Paul E. McKenney
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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