From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PULL 0/1] Socket next patches
Date: Tue, 25 Aug 2020 11:52:33 +0100 [thread overview]
Message-ID: <20200825105234.634767-1-berrange@redhat.com> (raw)
The following changes since commit 44423107e7b5731ef40c5c8632a5bad8b49d0838:
Merge remote-tracking branch 'remotes/xtensa/tags/20200821-xtensa' into staging (2020-08-24 19:55:23 +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 74a57ddc02c41f8f4bb549cedb107c1086daba58:
tests: fix a memory in test_socket_unix_abstract_good (2020-08-25 11:49:49 +0100)
----------------------------------------------------------------
Add support for UNIX sockets in the abstract namespace
----------------------------------------------------------------
Li Qiang (1):
tests: fix a memory in test_socket_unix_abstract_good
tests/test-util-sockets.c | 1 +
1 file changed, 1 insertion(+)
--
2.26.2
next reply other threads:[~2020-08-25 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 10:52 Daniel P. Berrangé [this message]
2020-08-25 10:52 ` [PULL 1/1] tests: fix a memory in test_socket_unix_abstract_good Daniel P. Berrangé
2020-08-25 19:48 ` [PULL 0/1] Socket next patches Peter Maydell
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=20200825105234.634767-1-berrange@redhat.com \
--to=berrange@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 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).