qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-fs@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Virtio-fs] [PATCH] virtiofsd: fix "filed" -> "failed" typo in error message
Date: Tue, 3 Sep 2019 18:35:11 +0100	[thread overview]
Message-ID: <20190903173511.GW2744@work-vm> (raw)
In-Reply-To: <20190827142340.23811-1-stefanha@redhat.com>

* Stefan Hajnoczi (stefanha@redhat.com) wrote:
> Reported-by: Jun Piao <piaojun@huawei.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>

Thanks, squashed into 'virtiofsd: passthrough_ll: add fallback for racy
ops'

Dave

> ---
> Based-on: <20190823092401.11883-1-stefanha@redhat.com>
>           ("[PATCH 0/2] virtiofsd: use "fuse_log.h" APIs instead of <err.h>")
> 
>  contrib/virtiofsd/passthrough_ll.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/contrib/virtiofsd/passthrough_ll.c b/contrib/virtiofsd/passthrough_ll.c
> index f348b0be9d..ff0c446187 100644
> --- a/contrib/virtiofsd/passthrough_ll.c
> +++ b/contrib/virtiofsd/passthrough_ll.c
> @@ -673,7 +673,7 @@ retry:
>  	}
>  	if (stat.st_dev != inode->key.dev || stat.st_ino != inode->key.ino) {
>  		if (!retries)
> -			fuse_warning("lo_parent_and_name: filed to match last\n");
> +			fuse_warning("lo_parent_and_name: failed to match last\n");
>  		goto fail_unref;
>  	}
>  	*parent = p;
> -- 
> 2.21.0
> 
> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


      reply	other threads:[~2019-09-03 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 14:23 [Qemu-devel] [PATCH] virtiofsd: fix "filed" -> "failed" typo in error message Stefan Hajnoczi
2019-09-03 17:35 ` Dr. David Alan Gilbert [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=20190903173511.GW2744@work-vm \
    --to=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=virtio-fs@redhat.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).