From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Xie, Huawei" <huawei.xie-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH v4 3/3] vhost: Check offset value
Date: Wed, 05 Nov 2014 18:00:31 +0100 [thread overview]
Message-ID: <2415734.hoAF1yVSAI@xps13> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F2E2149-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-05 16:52, Xie, Huawei:
> Why don't we merge 1,2,3 patches?
Because it's simpler to understand small patches with a dedicated
explanation in the commit log of each patch.
Why do you want to merge them?
--
Thomas
next prev parent reply other threads:[~2014-11-05 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 9:00 [PATCH] vhost: Fix packet length issue Ouyang Changchun
[not found] ` <1414659602-10115-1-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-10-30 14:59 ` [PATCH v2] " Ouyang Changchun
[not found] ` <1414681176-13965-1-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-04 7:05 ` [PATCH v3 0/2] " Ouyang Changchun
[not found] ` <1415084708-8192-1-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-04 7:05 ` [PATCH v3 1/2] vhost: " Ouyang Changchun
2014-11-04 7:05 ` [PATCH v3 2/2] vhost: Remove duplicated codes Ouyang Changchun
2014-11-05 7:10 ` [PATCH v4 0/3] Fix packet length issue Ouyang Changchun
[not found] ` <1415171435-24252-1-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-05 7:10 ` [PATCH v4 1/3] vhost: " Ouyang Changchun
[not found] ` <1415171435-24252-2-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-05 16:46 ` Xie, Huawei
2014-11-05 7:10 ` [PATCH v4 2/3] vhost: Remove duplicated codes Ouyang Changchun
2014-11-05 7:10 ` [PATCH v4 3/3] vhost: Check offset value Ouyang Changchun
[not found] ` <1415171435-24252-4-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-11-05 16:52 ` Xie, Huawei
[not found] ` <C37D651A908B024F974696C65296B57B0F2E2149-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-05 17:00 ` Thomas Monjalon [this message]
2014-11-05 17:05 ` Xie, Huawei
2014-11-06 0:44 ` Ouyang, Changchun
2014-11-05 9:28 ` [PATCH v4 0/3] Fix packet length issue Ananyev, Konstantin
[not found] ` <2601191342CEEE43887BDE71AB977258213A27BD-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-11-05 22:07 ` Thomas Monjalon
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=2415734.hoAF1yVSAI@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=huawei.xie-ral2JQCrhuEAvxtiuMwx3w@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.