From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>, Riku Voipio <riku.voipio@iki.fi>
Subject: [Qemu-devel] [PULL 0/2] Linux user for 4.0 patches
Date: Mon, 8 Apr 2019 21:37:09 +0200 [thread overview]
Message-ID: <20190408193711.32680-1-laurent@vivier.eu> (raw)
The following changes since commit f55a585d1037e5de6088f25e75443c2776786e29:
Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2019-04-07 14:54:55 +0100)
are available in the Git repository at:
git://github.com/vivier/qemu.git tags/linux-user-for-4.0-pull-request
for you to fetch changes up to 71ba74f67eaca21b0cc9d96f534ad3b9a7161400:
linux-user: rename gettid() to sys_gettid() to avoid clash with glibc (2019-04-08 17:27:13 +0200)
----------------------------------------------------------------
fix gettid() clash with new glibc
----------------------------------------------------------------
Daniel P. Berrangé (2):
linux-user: assume __NR_gettid always exists
linux-user: rename gettid() to sys_gettid() to avoid clash with glibc
linux-user/syscall.c | 19 ++++++-------------
1 file changed, 6 insertions(+), 13 deletions(-)
--
2.20.1
WARNING: multiple messages have this Message-ID (diff)
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] [PULL 0/2] Linux user for 4.0 patches
Date: Mon, 8 Apr 2019 21:37:09 +0200 [thread overview]
Message-ID: <20190408193711.32680-1-laurent@vivier.eu> (raw)
Message-ID: <20190408193709.ZBhWeuZTTmDdNAygms-QSNsCsZNl8xtDV0U0jgrwSAU@z> (raw)
The following changes since commit f55a585d1037e5de6088f25e75443c2776786e29:
Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2019-04-07 14:54:55 +0100)
are available in the Git repository at:
git://github.com/vivier/qemu.git tags/linux-user-for-4.0-pull-request
for you to fetch changes up to 71ba74f67eaca21b0cc9d96f534ad3b9a7161400:
linux-user: rename gettid() to sys_gettid() to avoid clash with glibc (2019-04-08 17:27:13 +0200)
----------------------------------------------------------------
fix gettid() clash with new glibc
----------------------------------------------------------------
Daniel P. Berrangé (2):
linux-user: assume __NR_gettid always exists
linux-user: rename gettid() to sys_gettid() to avoid clash with glibc
linux-user/syscall.c | 19 ++++++-------------
1 file changed, 6 insertions(+), 13 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-08 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 19:37 Laurent Vivier [this message]
2019-04-08 19:37 ` [Qemu-devel] [PULL 0/2] Linux user for 4.0 patches Laurent Vivier
2019-04-08 19:37 ` [Qemu-devel] [PULL 1/2] linux-user: assume __NR_gettid always exists Laurent Vivier
2019-04-08 19:37 ` Laurent Vivier
2019-04-08 19:37 ` [Qemu-devel] [PULL 2/2] linux-user: rename gettid() to sys_gettid() to avoid clash with glibc Laurent Vivier
2019-04-08 19:37 ` Laurent Vivier
2019-04-09 11:58 ` [Qemu-devel] [PULL 0/2] Linux user for 4.0 patches Peter Maydell
2019-04-09 11:58 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2019-01-10 8:37 Laurent Vivier
2019-01-10 18:45 ` Peter Maydell
2019-01-13 21:17 ` no-reply
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=20190408193711.32680-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).