qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: Carlo Arenas <carenas@gmail.com>
Cc: qemu-devel@nongnu.org, laurent@vivier.eu
Subject: Re: [Qemu-devel] linux-user: refactor socket.h into architecture specific sockbits
Date: Mon, 16 Oct 2017 12:32:50 +0000	[thread overview]
Message-ID: <20171016123250.GB1918@kos.to> (raw)
In-Reply-To: <CAPUEspg5AO_XzLa1n3cCTrz+22WYk5BZrE28ufDjPP7Y3KN2+Q@mail.gmail.com>

On Wed, Oct 11, 2017 at 12:10:04AM -0700, Carlo Arenas wrote:
> ping

Thanks for your patience
 
> some of the patches already have a Reviewed-by as shown by :
> 
>   http://patchwork.ozlabs.org/patch/818378/

Can you send the series without the whitespace-only changes?
 
> On Mon, Sep 25, 2017 at 4:19 PM, Carlo Marcelo Arenas Belón
> <carenas@gmail.com> wrote:
> > the definitions in socket.h are meant to reflect the ones in linux for each
> > respective target, but are sometimes difficult to maintain.
> >
> > hppa (AKA parisc) was initially merged with an independent file that mirrors
> > more closely the corresponding one in linux but hasn't been updated since.
> >
> > this series updates hppa with the latest bits from linux 4.14 and makes sure
> > all relevant architectures had a sockbits file that would be easy to maintain
> > going forward.
> >
> > most of the changes are pretty mechanical and I had made (thanks to Laurent's
> > tough review) every effort to ensure no value gets changed accidentaly and
> > all changes (even the ones where the value remains but is now in a different
> > base to better match what was used in the linux headers) are documented, so
> > it should be fairly safe and will fix bugs (mostly for sparc).
> >

  reply	other threads:[~2017-10-16 12:32 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
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 [this message]
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=20171016123250.GB1918@kos.to \
    --to=riku.voipio@iki.fi \
    --cc=carenas@gmail.com \
    --cc=laurent@vivier.eu \
    --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).