From: Alessandro Di Federico <ale+qemu@clearmind.me>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 1/3] Factor out {linux, bsd}-user/qemu.h
Date: Wed, 25 Jan 2017 08:37:01 +0100 [thread overview]
Message-ID: <E1cWIAK-0000hJ-EQ@clearmind.me> (raw)
In-Reply-To: <CAJ+F1CKqDZtyy3jXqTmk=juYAjm=8a-U4+_Pqtg3ikmQZ4BdvQ@mail.gmail.com>
On Tue, 24 Jan 2017 10:10:08 +0000
Marc-André Lureau <marcandre.lureau@gmail.com> wrote:
>
> Looks good. Probably worth to mention that the main difference is in
> commit 658f2dc970996d547a641b5685e384ebe6f2648e not being applied to
> bsd-user.
>
Yeah, I'll rebase my next patches on master.
My only doubt about this patch was whether the linux-* and bsd-*
implementations of put_user are equivalent. The linux one seems more
optimized, but they look equivalent to me.
--
Alessandro Di Federico
PhD student at Politecnico di Milano
next prev parent reply other threads:[~2017-01-25 7:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 8:45 [Qemu-devel] [RFC PATCH 0/3] Preparing the build system for libtcg Alessandro Di Federico
2017-01-21 8:45 ` [Qemu-devel] [RFC PATCH 1/3] Factor out {linux,bsd}-user/qemu.h Alessandro Di Federico
2017-01-24 10:10 ` [Qemu-devel] [RFC PATCH 1/3] Factor out {linux, bsd}-user/qemu.h Marc-André Lureau
2017-01-25 7:37 ` Alessandro Di Federico [this message]
2017-01-24 11:18 ` Peter Maydell
2017-01-25 7:38 ` Alessandro Di Federico
2017-02-07 17:25 ` Peter Maydell
2017-01-21 8:45 ` [Qemu-devel] [RFC PATCH 2/3] *-user targets object files decoupling Alessandro Di Federico
2017-01-24 10:09 ` Marc-André Lureau
2017-01-25 7:38 ` Alessandro Di Federico
2017-01-21 8:46 ` [Qemu-devel] [RFC PATCH 3/3] Introduce libtcg infrastructure Alessandro Di Federico
2017-01-24 10:08 ` Marc-André Lureau
2017-01-25 7:37 ` Alessandro Di Federico
2017-01-21 9:01 ` [Qemu-devel] [RFC PATCH 0/3] Preparing the build system for libtcg no-reply
2017-02-07 11:40 ` Peter Maydell
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=E1cWIAK-0000hJ-EQ@clearmind.me \
--to=ale+qemu@clearmind.me \
--cc=marcandre.lureau@gmail.com \
--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).