All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Ouyang,
	Changchun"
	<changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] librte_vhost: Fix the path test issue
Date: Thu, 06 Nov 2014 23:13:29 +0100	[thread overview]
Message-ID: <1838773.TXeSPBeZtt@xps13> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F2E3828-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

> > Commit aec8283d47d4e4366b6 fixes the compilation issue, but it leads to
> > one runtime issue: early exit wrongly. In some case, 'path' is NULL, but
> > 'resolved_path' has effective path, it should continue going ahead rather
> > than exit.
> > 
> > Signed-off-by: Changchun Ouyang <changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> Acked-by: Huawei Xie <huawei.xie-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Applied with Huawei's explanation.

Thanks
-- 
Thomas

      parent reply	other threads:[~2014-11-06 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  8:11 [PATCH] librte_vhost: Fix the path test issue Ouyang Changchun
     [not found] ` <1415002313-15661-1-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-06  2:38   ` Xie, Huawei
     [not found]     ` <C37D651A908B024F974696C65296B57B0F2E28C3-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-06  5:20       ` Ouyang, Changchun
     [not found]         ` <F52918179C57134FAEC9EA62FA2F9625118818BA-E2R4CRU6q/6iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-06 20:47           ` Xie, Huawei
2014-11-06 20:53   ` Xie, Huawei
     [not found]     ` <C37D651A908B024F974696C65296B57B0F2E3828-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-06 22:13       ` Thomas Monjalon [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=1838773.TXeSPBeZtt@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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.