From: Markus Armbruster <armbru@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
zxq_yx_007@163.com,
"marcandre lureau" <marcandre.lureau@redhat.com>,
"Li Qiang" <liq3ea@163.com>,
"Qemu Developers" <qemu-devel@nongnu.org>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH] tests: fix a memory in test_socket_unix_abstract_good
Date: Tue, 25 Aug 2020 07:59:07 +0200 [thread overview]
Message-ID: <87v9h7jmfo.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAKXe6SJ0+qvRQaKxirq=j9jAaKAdjXZzxVoMTbcQg_W=RcGz8g@mail.gmail.com> (Li Qiang's message of "Fri, 14 Aug 2020 00:32:30 +0800")
Li Qiang <liq3ea@gmail.com> writes:
> Hi Daniel,
> It seems this patch still not in the upstream.
Cc: qemu-trivial, hope this helps.
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
zxq_yx_007@163.com, "Li Qiang" <liq3ea@163.com>,
"Qemu Developers" <qemu-devel@nongnu.org>,
qemu-trivial@nongnu.org,
"marcandre lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH] tests: fix a memory in test_socket_unix_abstract_good
Date: Tue, 25 Aug 2020 07:59:07 +0200 [thread overview]
Message-ID: <87v9h7jmfo.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAKXe6SJ0+qvRQaKxirq=j9jAaKAdjXZzxVoMTbcQg_W=RcGz8g@mail.gmail.com> (Li Qiang's message of "Fri, 14 Aug 2020 00:32:30 +0800")
Li Qiang <liq3ea@gmail.com> writes:
> Hi Daniel,
> It seems this patch still not in the upstream.
Cc: qemu-trivial, hope this helps.
next prev parent reply other threads:[~2020-08-25 5:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 16:14 [PATCH] tests: fix a memory in test_socket_unix_abstract_good Li Qiang
2020-06-03 17:25 ` Philippe Mathieu-Daudé
2020-06-03 23:10 ` xiaoqiang zhao
2020-06-18 6:12 ` Li Qiang
2020-06-24 10:56 ` Daniel P. Berrangé
2020-08-13 16:32 ` Li Qiang
2020-08-25 5:59 ` Markus Armbruster [this message]
2020-08-25 5:59 ` Markus Armbruster
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=87v9h7jmfo.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=liq3ea@163.com \
--cc=liq3ea@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zxq_yx_007@163.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 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.