All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PULL 0/3] Socket next patches
Date: Thu, 21 May 2020 19:58:20 +0100	[thread overview]
Message-ID: <CAFEAcA_KQZysxZ3xx9xznh5xEdD=ja7pxh7U4oqb-XmFPP2WCg@mail.gmail.com> (raw)
In-Reply-To: <20200520130025.2201467-1-berrange@redhat.com>

On Wed, 20 May 2020 at 14:03, Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> The following changes since commit f2465433b43fb87766d79f42191607dac4aed5b4:
>
>   Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into staging (2020-05-19 13:42:58 +0100)
>
> are available in the Git repository at:
>
>   https://github.com/berrange/qemu tags/socket-next-pull-request
>
> for you to fetch changes up to e339273bfc514824410a49837e4f16dd4e51ae8e:
>
>   qemu-options: updates for abstract unix sockets (2020-05-20 10:34:53 +0100)
>
> ----------------------------------------------------------------
> Add support for UNIX sockets in the abstract namespace
>


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/5.1
for any user-visible changes.

-- PMM


      parent reply	other threads:[~2020-05-21 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 13:00 [PULL 0/3] Socket next patches Daniel P. Berrangé
2020-05-20 13:00 ` [PULL 1/3] qemu-sockets: add abstract UNIX domain socket support Daniel P. Berrangé
2020-05-20 14:23   ` Markus Armbruster
2020-05-20 14:33     ` Daniel P. Berrangé
2020-05-20 13:00 ` [PULL 2/3] tests/util-sockets: add abstract unix socket cases Daniel P. Berrangé
2020-05-20 13:00 ` [PULL 3/3] qemu-options: updates for abstract unix sockets Daniel P. Berrangé
2020-05-21 18:58 ` Peter Maydell [this message]

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='CAFEAcA_KQZysxZ3xx9xznh5xEdD=ja7pxh7U4oqb-XmFPP2WCg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.