From: Peter Maydell <peter.maydell@linaro.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Riku Voipio <riku.voipio@iki.fi>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/7] Linux user for 4.1 patches
Date: Fri, 10 May 2019 10:16:36 +0100 [thread overview]
Message-ID: <CAFEAcA8BAoqwdP-3cECUL2sLXQr_PxbdYBzMmZVEan3HcE8YVw@mail.gmail.com> (raw)
In-Reply-To: <20190510071557.30126-1-laurent@vivier.eu>
On Fri, 10 May 2019 at 08:18, Laurent Vivier <laurent@vivier.eu> wrote:
>
> The following changes since commit 68a7b9724fe80bedb85060bde605213ce3f9baec:
>
> Merge remote-tracking branch 'remotes/vivier2/tags/trivial-branch-pull-request' into staging (2019-05-09 13:36:10 +0100)
>
> are available in the Git repository at:
>
> git://github.com/vivier/qemu.git tags/linux-user-for-4.1-pull-request
>
> for you to fetch changes up to 6b333239ab1a4fa98f07f907f6268484a8514d1e:
>
> linux-user: fix GPROF build failure (2019-05-09 19:08:13 +0200)
>
> ----------------------------------------------------------------
> GPROF fixes, GCC9 fixes, SIOCGIFNAME fix, new IPV6 sockopts, elf fix
>
> ----------------------------------------------------------------
>
> Alex Bennée (2):
> linux-user: avoid treading on gprof's SIGPROF signals
> linux-user: fix GPROF build failure
>
> Alistair Francis (1):
> linux-user/elfload: Fix GCC 9 build warnings
>
> Daniel P. Berrangé (1):
> linux-user: avoid string truncation warnings in uname field copying
>
> Erik Kline via Qemu-devel (1):
> The ioctl(SIOCGIFNAME) call requires a struct ifreq.
Hi Laurent -- it looks like you forgot to fix up the
author email in this patch, so my pullreq-application
script complains:
[staging 181447e27a] Merge remote-tracking branch
'remotes/vivier2/tags/linux-user-for-4.1-pull-request' into staging
Date: Fri May 10 10:06:35 2019 +0100
Erik Kline via Qemu-devel (1):
The ioctl(SIOCGIFNAME) call requires a struct ifreq.
ERROR: pull request includes commits attributed to list
Could you fix it up and resubmit the pull, please?
thanks
-- PMM
next prev parent reply other threads:[~2019-05-10 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 7:15 [Qemu-devel] [PULL 0/7] Linux user for 4.1 patches Laurent Vivier
2019-05-10 7:15 ` [Qemu-devel] [PULL 1/7] linux-user: Add missing IPV6 sockopts Laurent Vivier
2019-05-10 7:15 ` [Qemu-devel] [PULL 2/7] linux-user/elfload: Fix GCC 9 build warnings Laurent Vivier
2019-05-10 7:15 ` [Qemu-devel] [PULL 3/7] linux-user: avoid string truncation warnings in uname field copying Laurent Vivier
2019-05-10 7:15 ` [Qemu-devel] [PULL 4/7] The ioctl(SIOCGIFNAME) call requires a struct ifreq Laurent Vivier
2019-05-10 7:15 ` [Qemu-devel] [PULL 5/7] linux-user: elf: Map empty PT_LOAD segments Laurent Vivier
2019-05-10 7:15 ` [Qemu-devel] [PULL 6/7] linux-user: avoid treading on gprof's SIGPROF signals Laurent Vivier
2019-05-10 7:15 ` [Qemu-devel] [PULL 7/7] linux-user: fix GPROF build failure Laurent Vivier
2019-05-10 9:16 ` Peter Maydell [this message]
2019-05-10 10:47 ` [Qemu-devel] [PULL 0/7] Linux user for 4.1 patches 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=CAFEAcA8BAoqwdP-3cECUL2sLXQr_PxbdYBzMmZVEan3HcE8YVw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--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 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).