From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>, Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PATCH v2 0/2] Add pseudo /proc/hardware and /proc/cpuinfo
Date: Fri, 17 May 2019 15:31:47 +0200 [thread overview]
Message-ID: <20190517133149.19593-1-laurent@vivier.eu> (raw)
They are used by some package setup scripts to set the default configuration.
v2: rebase
Laurent Vivier (2):
linux-user: add pseudo /proc/cpuinfo for sparc
linux-user: add pseudo /proc/hardware for m68k
linux-user/syscall.c | 27 ++++++++++++++++++++++++++-
1 file changed, 26 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2019-05-17 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 13:31 Laurent Vivier [this message]
2019-05-17 13:31 ` [Qemu-devel] [PATCH v2 1/2] linux-user: add pseudo /proc/cpuinfo for sparc Laurent Vivier
2019-05-20 3:03 ` Richard Henderson
2019-05-17 13:31 ` [Qemu-devel] [PATCH v2 2/2] linux-user: add pseudo /proc/hardware for m68k Laurent Vivier
2019-05-20 3:03 ` Richard Henderson
2019-05-20 10:57 ` [Qemu-devel] [PATCH v2 0/2] Add pseudo /proc/hardware and /proc/cpuinfo Philippe Mathieu-Daudé
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=20190517133149.19593-1-laurent@vivier.eu \
--to=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).