All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: arnd@arndb.de, david.laight@aculab.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	tanyuan@tinylab.org, thomas@t-8ch.de
Subject: Re: [PATCH v6 2/2] tools/nolibc: fix up size inflate regression
Date: Tue, 15 Aug 2023 14:17:17 +0200	[thread overview]
Message-ID: <ZNtszQeigYuItaKA@1wt.eu> (raw)
In-Reply-To: <20230813133944.19604-1-falcon@tinylab.org>

On Sun, Aug 13, 2023 at 09:39:44PM +0800, Zhangjin Wu wrote:
> > And we're done, you can then keep the simplified __sysret() macro for all
> > other call places.
> > 
> 
> Now, this issue is near to the end ;-)

I've now pushed the simplified fix (without changing the SET_ERRNO()
macro, enough last minute breaking changes for now) in branch
20230815-for-6.6-2.

The tests pass and riscv/loongarch are even very slightly smaller than
before (~8 bytes) but again that doesn't count as it depends on how the
compiler decides to arrange if/else branches.

I'll let Shuah know about these late fixes.

Regards,
Willy

  parent reply	other threads:[~2023-08-15 12:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 21:49 [PATCH v6 0/2] tools/nolibc: fix up size inflat regression Zhangjin Wu
2023-08-11 21:50 ` [PATCH v6 1/2] tools/nolibc: let sys_brk, sys_mmap and sys_mmap2 return long Zhangjin Wu
2023-08-11 21:51 ` [PATCH v6 2/2] tools/nolibc: fix up size inflate regression Zhangjin Wu
2023-08-13  9:00   ` Willy Tarreau
2023-08-13 13:39     ` Zhangjin Wu
2023-08-14  7:25       ` Willy Tarreau
2023-08-15 12:17       ` Willy Tarreau [this message]
2023-08-15 16:34         ` Zhangjin Wu
2023-08-13  9:08 ` [PATCH v6 0/2] tools/nolibc: fix up size inflat regression Willy Tarreau
2023-08-13 13:56   ` Zhangjin Wu

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=ZNtszQeigYuItaKA@1wt.eu \
    --to=w@1wt.eu \
    --cc=arnd@arndb.de \
    --cc=david.laight@aculab.com \
    --cc=falcon@tinylab.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=tanyuan@tinylab.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.