qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: AlexChen <alex.chen@huawei.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: zhang.zhanghailiang@huawei.com, qemu-trivial@nongnu.org,
	mjt@tls.msk.ru, Laurent Vivier <laurent@vivier.eu>,
	qemu-devel@nongnu.org, zhengchuan@huawei.com
Subject: Re: [PATCH 1/2] plugins: Fix resource leak in connect_socket()
Date: Fri, 6 Nov 2020 09:40:38 +0800	[thread overview]
Message-ID: <5FA4A996.5040500@huawei.com> (raw)
In-Reply-To: <87ft5oay3z.fsf@linaro.org>

On 2020/11/5 18:37, Alex Bennée wrote:
> 
> AlexChen <alex.chen@huawei.com> writes:
> 
>> Kindly ping.
> 
> Ahh sorry I missed these. Was there a cover letter for the series?
> 

I forgot to send the cover letter, I will send the patch V2 with the cover letter.

Thanks,
Alex Chen


      reply	other threads:[~2020-11-06  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 13:45 [PATCH 1/2] plugins: Fix resource leak in connect_socket() AlexChen
2020-11-05  6:53 ` AlexChen
2020-11-05 10:37   ` Alex Bennée
2020-11-06  1:40     ` AlexChen [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=5FA4A996.5040500@huawei.com \
    --to=alex.chen@huawei.com \
    --cc=alex.bennee@linaro.org \
    --cc=laurent@vivier.eu \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.com \
    --cc=zhengchuan@huawei.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).