From: Carlo Arenas <carenas@gmail.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org, riku.voipio@iki.fi
Subject: Re: [Qemu-devel] [PATCH v2 6/6] linux_user: consolidate sock_type
Date: Tue, 17 Oct 2017 10:36:39 -0700 [thread overview]
Message-ID: <CAPUEspi9fL33R=mscXxYGfB55HWS9DqzYZN+Vdti2sccPsV16w@mail.gmail.com> (raw)
In-Reply-To: <5496192f-4fef-ef16-2769-81a9d31775d7@vivier.eu>
On Wed, Oct 11, 2017 at 6:23 AM, Laurent Vivier <laurent@vivier.eu> wrote:
> Le 26/09/2017 à 01:19, Carlo Marcelo Arenas Belón a écrit :
>> remove unnecessary sock_type enum and other unused surrounding code to
>> allow for per arch sockbits to mirror better linux headers for maintenance
>>
>> Signed-off-by: Carlo Marcelo Arenas Belón <carenas@gmail.com>
>> ---
>> linux-user/alpha/sockbits.h | 36 ----------------------------
>> linux-user/hppa/sockbits.h | 30 -----------------------
>> linux-user/mips/sockbits.h | 35 ---------------------------
>> linux-user/socket.h | 58 ++++++++++++++++++++++-----------------------
>> linux-user/sparc/sockbits.h | 35 ---------------------------
>> 5 files changed, 29 insertions(+), 165 deletions(-)
>
> I think it's not a good idea to mix again what we have just unmixed.
do you object to the fact it was done in 2 steps (first moving out
from socket.h and then added it back as a single block)? it was done
that way to reuse as much as possible the code that was already
reviewed.
the end result is the important part, though; and it is a sockbits.h
for those 4 architectures (and a socket.h for the rest) that could be
automatically generated or compared with the corresponding linux
headers and therefore hopefully be easier to maintain going forward.
since we are going to redo the series anyway, could we get some
discussion/agreement on the design of it?, have to admit I am a little
surprised by all the patches flying by the list but not many
conversations, and being new to qemu linux-user I think I could have
benefited from it to avoid some of the mistakes made.
Carlo
next prev parent reply other threads:[~2017-10-17 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 23:19 [Qemu-devel] linux-user: refactor socket.h into architecture specific sockbits Carlo Marcelo Arenas Belón
2017-09-25 23:19 ` [Qemu-devel] [PATCH v2 1/6] linux-user: update hppa sockbits Carlo Marcelo Arenas Belón
2017-09-25 23:19 ` [Qemu-devel] [PATCH v2 2/6] linux-user: refactor socket.h for alpha Carlo Marcelo Arenas Belón
2017-09-25 23:19 ` [Qemu-devel] [PATCH v2 3/6] linux-user: refactor socket.h for mips Carlo Marcelo Arenas Belón
2017-09-25 23:19 ` [Qemu-devel] [PATCH v2 4/6] linux-user: refactor socket.h for sparc Carlo Marcelo Arenas Belón
2017-09-25 23:19 ` [Qemu-devel] [PATCH v2 5/6] linux-user: update default socket.h Carlo Marcelo Arenas Belón
2017-09-25 23:19 ` [Qemu-devel] [PATCH v2 6/6] linux_user: consolidate sock_type Carlo Marcelo Arenas Belón
2017-10-11 13:23 ` Laurent Vivier
2017-10-17 17:36 ` Carlo Arenas [this message]
2017-10-11 12:58 ` [Qemu-devel] [PATCH v2 5/6] linux-user: update default socket.h Laurent Vivier
2017-10-11 8:00 ` [Qemu-devel] [PATCH v2 1/6] linux-user: update hppa sockbits Laurent Vivier
2017-10-11 7:10 ` [Qemu-devel] linux-user: refactor socket.h into architecture specific sockbits Carlo Arenas
2017-10-16 12:32 ` Riku Voipio
2017-10-17 14:35 ` Carlo Arenas
2017-10-20 7:25 ` Laurent Vivier
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='CAPUEspi9fL33R=mscXxYGfB55HWS9DqzYZN+Vdti2sccPsV16w@mail.gmail.com' \
--to=carenas@gmail.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).