All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel <qemu-devel@nongnu.org>, Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH 5/5] linux-user: add sparc/sparc64 specific errno
Date: Tue, 8 May 2018 13:22:46 -0700	[thread overview]
Message-ID: <CAMo8BfJv_Sg8EhjrUcS-wjbwwiLgv2kY4-GaxtXTygs19hUMqQ@mail.gmail.com> (raw)
In-Reply-To: <20180508194026.1281-6-laurent@vivier.eu>

On Tue, May 8, 2018 at 12:40 PM, Laurent Vivier <laurent@vivier.eu> wrote:
> Copied from linux/arch/sparc/include/uapi/asm/errno.h
>
> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
> ---
>  linux-user/sparc/target_syscall.h   | 203 ++++++++++++++++++++++++++++++++++++
>  linux-user/sparc64/target_syscall.h | 203 ++++++++++++++++++++++++++++++++++++
>  2 files changed, 406 insertions(+)

The changes are coming from single file, why duplicating them?
Could they go into e.g. linux-user/sparc/target_errno.h, and get
#included by both linux-user/sparc/target_syscall.h and
linux-user/sparc64/target_syscall.h?

-- 
Thanks.
-- Max

  reply	other threads:[~2018-05-08 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 19:40 [Qemu-devel] [PATCH 0/5] linux-user: fix sparc32plus Laurent Vivier
2018-05-08 19:40 ` [Qemu-devel] [PATCH 1/5] linux-user: define correct fcntl() values for sparc Laurent Vivier
2018-05-08 20:01   ` Max Filippov
2018-05-08 19:40 ` [Qemu-devel] [PATCH 2/5] linux-user: fix flock/flock64 padding Laurent Vivier
2018-05-08 20:08   ` Max Filippov
2018-05-08 19:40 ` [Qemu-devel] [PATCH 3/5] linux-user: update sparc/syscall_nr.h to linux header 4.16 Laurent Vivier
2018-05-08 19:40 ` [Qemu-devel] [PATCH 4/5] linux-user: fix convertion of flock/flock64 l_type field Laurent Vivier
2018-05-08 19:40 ` [Qemu-devel] [PATCH 5/5] linux-user: add sparc/sparc64 specific errno Laurent Vivier
2018-05-08 20:22   ` Max Filippov [this message]
2018-05-08 20:26     ` 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=CAMo8BfJv_Sg8EhjrUcS-wjbwwiLgv2kY4-GaxtXTygs19hUMqQ@mail.gmail.com \
    --to=jcmvbkbc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.