All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Li Qiang <liq3ea@gmail.com>
Cc: qemu-devel@nongnu.org, liqiang6-s@360.cn
Subject: Re: [Qemu-devel] [PATCH 0/3] add cleanup operation in handle/proxy backend
Date: Mon, 14 Nov 2016 17:53:11 +0100	[thread overview]
Message-ID: <20161114175311.069ef717@bahia> (raw)
In-Reply-To: <5829af05.84f4420a.a436f.4a62@mx.google.com>

Hi Li,

On Mon, 14 Nov 2016 07:32:55 -0500
Li Qiang <liq3ea@gmail.com> wrote:

> From: Li Qiang <liq3ea@gmail.com>
> 
> Currently, the backend of VirtFS doesn't have a cleanup
> function. This will leak some resources in handle and proxy
> backend driver. This patchset addresses this issue.
> 
> Li Qiang (3):
>   9pfs: add cleanup operation in FileOperations
>   9pfs: add cleanup operation for handle backend driver
>   9pfs: add cleanup operation for proxy backend driver
> 
>  fsdev/file-op-9p.h  |  1 +
>  hw/9pfs/9p-handle.c |  8 ++++++++
>  hw/9pfs/9p-proxy.c  | 10 ++++++++++
>  hw/9pfs/9p.c        |  3 +++
>  4 files changed, 22 insertions(+)
> 

The series ends up unthreaded again...

This is what we have in the cover (0/3):

Message-ID: <5829af05.84f4420a.a436f.4a62@mx.google.com>
X-Google-Original-Message-ID: <1479126778-125867-1-git-send-email-Qiang(liqiang6-s@360.cn)>

but the patches have:

In-Reply-To: <1479126778-125867-1-git-send-email-Qiang(liqiang6-s@360.cn)>
References: <1479126778-125867-1-git-send-email-Qiang(liqiang6-s@360.cn)>

A quick research seems to indicate that gmail rewrites message-id if it does
not follow the <user@domain> format, which is obviously the case here.

Please fix that before you post again.

Cheers.

--
Greg

      reply	other threads:[~2016-11-14 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 12:32 [Qemu-devel] [PATCH 0/3] add cleanup operation in handle/proxy backend Li Qiang
2016-11-14 16:53 ` Greg Kurz [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=20161114175311.069ef717@bahia \
    --to=groug@kaod.org \
    --cc=liq3ea@gmail.com \
    --cc=liqiang6-s@360.cn \
    --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.