From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: Nikita Ivanov <nivanov@cloudlinux.com>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Greg Kurz" <groug@kaod.org>, "Jason Wang" <jasowang@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Konstantin Kostiuk" <kkostiuk@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Bin Meng" <bmeng.cn@gmail.com>
Subject: Re: [PATCH v2 2/2] error handling: Use RETRY_ON_EINTR() macro where applicable
Date: Wed, 12 Oct 2022 17:43:00 +0200 [thread overview]
Message-ID: <2564015.mS1nRVYtUv@silver> (raw)
In-Reply-To: <CAEUhbmU561dwFmVCqZG7WdTUhRtfSR_wB8pa0KP2YVXwyHaZuQ@mail.gmail.com>
On Mittwoch, 12. Oktober 2022 17:17:46 CEST Bin Meng wrote:
> Hi,
>
> On Wed, Oct 12, 2022 at 8:32 PM Nikita Ivanov <nivanov@cloudlinux.com> wrote:
> > There is a defined RETRY_ON_EINTR() macro in qemu/osdep.h which
> > handles the same while loop.
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/415
> >
> > Signed-off-by: Nikita Ivanov <nivanov@cloudlinux.com>
> > ---
> >
> > block/file-posix.c | 37 ++++++++++++++++---------------------
> > chardev/char-pty.c | 4 +---
> > hw/9pfs/9p-local.c | 8 ++------
> > net/l2tpv3.c | 17 +++++------------
> > net/socket.c | 16 +++++++---------
> > net/tap.c | 12 ++++--------
> > qga/commands-posix.c | 4 +---
> > semihosting/syscalls.c | 4 +---
> > tests/qtest/libqtest.c | 14 ++++++--------
> > tests/vhost-user-bridge.c | 4 +---
> > util/main-loop.c | 4 +---
> > util/osdep.c | 4 +---
> > util/vfio-helpers.c | 12 ++++++------
> > 13 files changed, 52 insertions(+), 88 deletions(-)
>
> This patch has to be squashed into patch 1 for bisectability, as TFR
> is already removed in patch 1.
They are intentionally separated: 1st patch replaces occurrences of TFR,
whereas 2nd patch introduces use of macro at locations where not used yet.
Nikita, could you please move those 2 hunks that still had TFR() occurrence to
patch 1?
And please use git's --thread option next time, so that individual patch
emails are linked to cover letter email (which adds appropriate `References:`
and `In-Reply-To:` email headers).
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2022-10-12 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 12:31 [PATCH v2 2/2] error handling: Use RETRY_ON_EINTR() macro where applicable Nikita Ivanov
2022-10-12 15:03 ` Marc-André Lureau
2022-10-12 15:17 ` Bin Meng
2022-10-12 15:43 ` Christian Schoenebeck [this message]
2022-10-12 16:05 ` Nikita Ivanov
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=2564015.mS1nRVYtUv@silver \
--to=qemu_oss@crudebyte.com \
--cc=armbru@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=groug@kaod.org \
--cc=jasowang@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=nivanov@cloudlinux.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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).