From: Richard Henderson <richard.henderson@linaro.org>
To: Nathan Egge <negge@xiph.org>, qemu-devel@nongnu.org
Cc: akihiko.odaki@daynix.com, deller@gmx.de
Subject: Re: [PATCH v9 07/24] linux-user: Do not call get_errno() in do_brk()
Date: Fri, 4 Aug 2023 21:26:18 -0700 [thread overview]
Message-ID: <0c0faac4-952a-1f23-3b43-3b15e6d5f24b@linaro.org> (raw)
In-Reply-To: <d83d4d31-dabd-5f05-e173-cbe255e26aed@xiph.org>
On 8/4/23 16:40, Nathan Egge wrote:
> The linux-user/syscall.c has many such places where this style check is failing. Should
> these be fixed in a separate patch?
Yes, eventually.
r~
next prev parent reply other threads:[~2023-08-05 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 23:40 [PATCH v9 07/24] linux-user: Do not call get_errno() in do_brk() Nathan Egge
2023-08-05 4:26 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-04 22:00 [PATCH v9 for-8.1 00/24] linux-user + tcg patch queue Richard Henderson
2023-08-04 22:00 ` [PATCH v9 07/24] linux-user: Do not call get_errno() in do_brk() Richard Henderson
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=0c0faac4-952a-1f23-3b43-3b15e6d5f24b@linaro.org \
--to=richard.henderson@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=deller@gmx.de \
--cc=negge@xiph.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).