qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PULL 0/9] slirp updates
Date: Fri, 1 Jun 2018 14:50:29 +0100	[thread overview]
Message-ID: <CAFEAcA8w6W546wFg099RWXKPERWeeh96zPiAoQUqSodawXmgDg@mail.gmail.com> (raw)
In-Reply-To: <20180531192237.3994-1-samuel.thibault@ens-lyon.org>

On 31 May 2018 at 20:22, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> The following changes since commit c181ddaa176856b3cd2dfd12bbcf25fa9c884a97:
>
>   Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180531-1' into staging (2018-05-31 17:00:55 +0100)
>
> are available in the Git repository at:
>
>   http://people.debian.org/~sthibault/qemu.git tags/samuel-thibault
>
> for you to fetch changes up to 528e913612bf22661b169018780d8a6fc678c655:
>
>   slirp/ncsi: add checksum support (2018-05-31 20:45:02 +0200)
>
> ----------------------------------------------------------------
> slirp updates
>
> Alexey Kardashevskiy
>   slirp: Improve debugging messages
>
> Andreas Gustafsson, Samuel Thibault, James Clarke
>   slirp: Improve bandwidth in GDB remote debugging and FreeBSD guests
>
> Benjamin Drung:
>   slirp/dhcp: Add domainname option

Hi; it looks like you forgot to add your signed-off-by to this
patch from Benjamin. Could you add it and respin, please?
(You can just send the pullreq cover letter, no need to re-email
the individual patches.)

thanks
-- PMM

  parent reply	other threads:[~2018-06-01 13:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 19:22 [Qemu-devel] [PULL 0/9] slirp updates Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 1/9] slirp: Add domainname option to slirp's DHCP server Samuel Thibault
2018-05-31 19:42   ` Eric Blake
2018-05-31 19:22 ` [Qemu-devel] [PULL 2/9] slirp: disable Nagle in outgoing connections Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 3/9] slirp: disable Nagle in ingoing connections Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 4/9] slirp/debug: Print IP addresses in human readable form Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 5/9] net/slirp: Convert atoi to qemu_strtoi to allow error checking Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 6/9] slirp: Send window updates to guest after window was closed Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 7/9] slirp/ncsi: fix "Get Version ID" payload length Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 8/9] slirp/ncsi: add a "Get Parameters" response Samuel Thibault
2018-05-31 19:22 ` [Qemu-devel] [PULL 9/9] slirp/ncsi: add checksum support Samuel Thibault
2018-05-31 19:40 ` [Qemu-devel] [PULL 0/9] slirp updates no-reply
2018-06-01 13:50 ` Peter Maydell [this message]
2018-06-01 13:57   ` Samuel Thibault
  -- strict thread matches above, loose matches on Subject: below --
2017-04-29 16:47 Samuel Thibault
2017-04-29 17:28 ` no-reply
2017-05-02 14:16 ` Stefan Hajnoczi

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=CAFEAcA8w6W546wFg099RWXKPERWeeh96zPiAoQUqSodawXmgDg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefanha@redhat.com \
    /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).