From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH 02/16] h8300: UAPI headers
Date: Thu, 22 Jan 2015 02:16:28 +0900 [thread overview]
Message-ID: <87twzkkqab.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <1621236.pdeBUC53s3@wuerfel>
At Wed, 21 Jan 2015 09:46:58 +0100,
Arnd Bergmann wrote:
>
> On Wednesday 21 January 2015 13:23:57 Yoshinori Sato wrote:
> > Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> >
> > create mode 100644 arch/h8300/include/uapi/asm/Kbuild
> > create mode 100644 arch/h8300/include/uapi/asm/auxvec.h
> > create mode 100644 arch/h8300/include/uapi/asm/byteorder.h
> > create mode 100644 arch/h8300/include/uapi/asm/ptrace.h
> > create mode 100644 arch/h8300/include/uapi/asm/sigcontext.h
> > create mode 100644 arch/h8300/include/uapi/asm/signal.h
> > create mode 100644 arch/h8300/include/uapi/asm/swab.h
> > create mode 100644 arch/h8300/include/uapi/asm/unistd.h
>
> In the introductory mail, you mention that you have a new toolchain.
> I assume this implies that all existing user space binaries are
> incompatible with new kernels. If so, I would like to ask you
> to use the generic ABI where possible. In particular, using
> asm-generic/unistd.h to get the default system call table that
> is now shared across all new architectures, but
> asm-generic/signal.h also looks like it could be used here
> and asm-generic/swab.h might work but depends on performance
> considerations.
>
Hmm...
I think old ABI compatibility is not needed. Because toolchain
not have compatibility.
unistd.h is agree.
signal.h and swab.h is considered.
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arch" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
next prev parent reply other threads:[~2015-01-21 17:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1421813622.git.ysato@users.sourceforge.jp>
2015-01-21 4:23 ` [PATCH 01/16] h8300: Assembly headers Yoshinori Sato
2015-01-21 11:02 ` Geert Uytterhoeven
2015-01-21 17:22 ` Yoshinori Sato
2015-01-21 4:23 ` [PATCH 02/16] h8300: UAPI headers Yoshinori Sato
2015-01-21 8:46 ` Arnd Bergmann
2015-01-21 17:16 ` Yoshinori Sato [this message]
2015-01-21 4:24 ` [PATCH 03/16] h8300: defconfigs Yoshinori Sato
2015-01-21 8:47 ` Arnd Bergmann
2015-01-21 4:24 ` [PATCH 04/16] h8300: Memory management Yoshinori Sato
2015-01-21 10:57 ` Geert Uytterhoeven
2015-01-21 17:20 ` Yoshinori Sato
2015-01-21 4:25 ` [PATCH 05/16] h8300: Target depend (hw define) part Yoshinori Sato
2015-01-21 4:27 ` [PATCH 06/16] drivers: Add h8300 Yoshinori Sato
2015-01-21 11:03 ` Geert Uytterhoeven
2015-01-21 17:23 ` Yoshinori Sato
2015-01-21 4:29 ` [PATCH 07/16] Add ELF machine Yoshinori Sato
2015-01-21 4:29 ` [PATCH 08/16] h8300: Build scripts Yoshinori Sato
2015-01-21 4:30 ` [PATCH 09/16] h8300: kernel startup Yoshinori Sato
2015-01-21 4:30 ` [PATCH 10/16] h8300: Exception and Interrupt handler Yoshinori Sato
2015-01-21 4:31 ` [PATCH 11/16] h8300: Libraries Yoshinori Sato
2015-01-21 4:31 ` [PATCH 12/16] h8300: clocksource Yoshinori Sato
2015-01-21 8:49 ` Arnd Bergmann
2015-01-21 17:06 ` Yoshinori Sato
2015-01-21 4:31 ` [PATCH 13/16] h8300: ptrace helper Yoshinori Sato
2015-01-21 8:51 ` Arnd Bergmann
2015-01-21 17:08 ` Yoshinori Sato
2015-01-21 4:32 ` [PATCH 14/16] h8300: signal handler Yoshinori Sato
2015-01-21 4:32 ` [PATCH 15/16] h8300: system call entry table Yoshinori Sato
2015-01-21 4:32 ` [PATCH 16/16] h8300: misc functions Yoshinori Sato
2015-01-21 9:01 ` Arnd Bergmann
2015-01-21 17:19 ` Yoshinori Sato
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=87twzkkqab.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.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 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.