From: riku.voipio@linaro.org
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Riku Voipio <riku.voipio@linaro.org>
Subject: [Qemu-devel] [PATCH 0/4] linux-user: uname release cleanup
Date: Tue, 4 Mar 2014 05:21:57 +0200 [thread overview]
Message-ID: <1393903321-6352-1-git-send-email-riku.voipio@linaro.org> (raw)
From: Riku Voipio <riku.voipio@linaro.org>
Currently some distributors use --enable-uname-release=2.6.32 or
something similar to allow running new target binaries on
old host systems.
In 4a24a758101ff726c9bd3b867e12d5580c793af0 and more flexible
solution was created. However, if you continue to compile with
the --enable-uname-release option, the new way will be overriden.
To make sure people stop using the old way when 2.0 gets released,
move all targets to the new way, and remove the old configure option.
Riku Voipio (4):
linux-user: rename cpu-uname -> uname
linux-user: move uname functions to uname.c
linux-user: set minimum kernel version to 2.6.32
linux-user: remove configure option for setting uname release
configure | 8 --
linux-user/Makefile.objs | 2 +-
linux-user/alpha/syscall.h | 1 +
linux-user/arm/syscall.h | 1 +
linux-user/cpu-uname.c | 72 -----------------
linux-user/cpu-uname.h | 1 -
linux-user/cris/syscall.h | 2 +-
linux-user/i386/syscall.h | 1 +
linux-user/m68k/syscall.h | 2 +-
linux-user/main.c | 2 +-
linux-user/microblaze/syscall.h | 2 +-
linux-user/mips/syscall.h | 1 +
linux-user/mips64/syscall.h | 1 +
linux-user/openrisc/syscall.h | 1 +
linux-user/ppc/syscall.h | 1 +
linux-user/s390x/syscall.h | 1 +
linux-user/sh4/syscall.h | 1 +
linux-user/sparc/syscall.h | 1 +
linux-user/sparc64/syscall.h | 1 +
linux-user/syscall.c | 104 +-----------------------
linux-user/uname.c | 171 ++++++++++++++++++++++++++++++++++++++++
linux-user/uname.h | 10 +++
linux-user/unicore32/syscall.h | 1 +
linux-user/x86_64/syscall.h | 1 +
24 files changed, 200 insertions(+), 189 deletions(-)
delete mode 100644 linux-user/cpu-uname.c
delete mode 100644 linux-user/cpu-uname.h
create mode 100644 linux-user/uname.c
create mode 100644 linux-user/uname.h
--
1.8.1.2
reply other threads:[~2014-03-04 3:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1393903321-6352-1-git-send-email-riku.voipio@linaro.org \
--to=riku.voipio@linaro.org \
--cc=peter.maydell@linaro.org \
--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).