All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 4/4 v2] vhost: fix wrong usage of eventfd_t
Date: Sun, 27 Sep 2015 08:17:17 +0800	[thread overview]
Message-ID: <20150927001717.GE2326@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1848599.sSxKKo3m0q@xps13>

On Fri, Sep 25, 2015 at 02:44:11PM +0200, Thomas Monjalon wrote:
> 2015-09-24 22:01, Yuanhan Liu:
> > Would you consider to apply these 4 patches please? The 4th patch
> > affects quite many lines of code, and the sooner we apply it, the
> > fewer chance it will introduce conflicts for later patches.
> 
> Yes, I'm checking it.
> 
> The patch 4/4 is v2. Other ones have no version.

Which means no changes for others in this version.

> When you'll send a new version of a new patchset, please
> - increment version number of every patches to the same number

And, I can do that.

> - make the first email the child of the previous version

I'm wondering how could you do that, with git-send-email.

	--yliu

  parent reply	other threads:[~2015-09-27  0:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09  5:34 [PATCH 1/4] vhost: remove redundant ; Yuanhan Liu
2015-09-09  5:34 ` [PATCH 2/4] vhost: fix typo Yuanhan Liu
2015-09-09  5:34 ` [PATCH 3/4] vhost: get rid of duplicate code Yuanhan Liu
2015-09-09  5:34 ` [PATCH 4/4 v2] vhost: fix wrong usage of eventfd_t Yuanhan Liu
2015-09-09  5:44   ` Xie, Huawei
2015-09-24 14:01     ` Yuanhan Liu
2015-09-25 12:44       ` Thomas Monjalon
2015-09-25 12:59         ` Thomas Monjalon
2015-09-27  0:17         ` Yuanhan Liu [this message]
2015-09-27 19:35           ` Thomas Monjalon
2015-10-08  6:29             ` Yuanhan Liu

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=20150927001717.GE2326@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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.