From: Panu Matilainen <pmatilai@redhat.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: add missing build dependency on librte_net
Date: Thu, 18 Feb 2016 16:07:52 +0200 [thread overview]
Message-ID: <56C5D038.2070700@redhat.com> (raw)
In-Reply-To: <20160218135603.GO21426@yliu-dev.sh.intel.com>
On 02/18/2016 03:56 PM, Yuanhan Liu wrote:
> On Thu, Feb 18, 2016 at 03:39:26PM +0200, Panu Matilainen wrote:
>> On 02/18/2016 03:25 PM, Yuanhan Liu wrote:
>>> On Thu, Feb 18, 2016 at 11:47:43AM +0200, Panu Matilainen wrote:
>>>> Commit d0cf91303d73 added dependency on librte_net headers to vhost
>>>> but did not add this to the Makefile, which makes builds
>>>> non-deterministic. Curiously it is non-parallel build that is
>>>> consistently broken by this missing dependency, usually it's the other
>>>> way around, but trying to build without -j(n) fails with:
>>>
>>> Yeah, I have confirmed it; I was wondering why I didn't meet such build
>>> error.
>>>
>>>>
>>>> dpdk/lib/librte_vhost/vhost_rxtx.c:41:20:
>>>> fatal error: rte_ip.h: No such file or directory
>>>>
>>>> Fixes: d0cf91303d73 ("vhost: add Tx offload capabilities")
>>>> Signed-off-by: Panu Matilainen <pmatilai@redhat.com>
>>>
>>> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
>>>
>>> Thanks.
>>>
>>> BTW, please cc me for virtio/vhost patches next time, otherwise, it's
>>> easily got overlooked: too many emails.
>>
>> Hmm, I thought I did. Looking more carefully now, I mixed up the patch
>> author (who was CC'd) with you:
>
> I didn't see the author was cc'ed from my email client:
>
> Date: Thu, 18 Feb 2016 11:47:43 +0200
> From: Panu Matilainen <pmatilai@redhat.com>
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] vhost: add missing build dependency on librte_net
Hmm, indeed. But this is what git told me (happened to have the whole
thing in scrollback buffer):
[pmatilai@sopuli dpdk]$ git send-email --cc="jijiang.liu@intel.com"
--cc="huawei.xie@intel.com" -1
/tmp/ZAW8ErlHWe/0001-vhost-add-missing-build-dependency-on-librte_net.patch
From: Panu Matilainen <pmatilai@redhat.com>
To: dev@dpdk.org
Cc: jijiang.liu@intel.com,
huawei.xie@intel.com
Subject: [PATCH] vhost: add missing build dependency on librte_net
Date: Thu, 18 Feb 2016 11:47:43 +0200
Message-Id:
<eef2b50186eea076a3a3ff9f10bd8c310a036549.1455788863.git.pmatilai@redhat.com>
X-Mailer: git-send-email 2.5.0
Send this email? ([y]es|[n]o|[q]uit|[a]ll): a
OK. Log says:
Server: smtp.corp.redhat.com
MAIL FROM:<pmatilai@redhat.com>
RCPT TO:<dev@dpdk.org>
RCPT TO:<jijiang.liu@intel.com>
RCPT TO:<huawei.xie@intel.com>
From: Panu Matilainen <pmatilai@redhat.com>
To: dev@dpdk.org
Cc: jijiang.liu@intel.com,
huawei.xie@intel.com
Subject: [PATCH] vhost: add missing build dependency on librte_net
Date: Thu, 18 Feb 2016 11:47:43 +0200
Message-Id:
<eef2b50186eea076a3a3ff9f10bd8c310a036549.1455788863.git.pmatilai@redhat.com>
X-Mailer: git-send-email 2.5.0
So where do the CC's vanish?
>>
>> commit d0cf91303d731997945420832ee245b21f292e19
>> Author: Jijiang Liu <jijiang.liu@intel.com>
>>
>> I hate it when people call me Paul (commonly happens) just because it
>
> Hmm... I didn't call you that, right?
No, not you :)
>> vaguely resembles my name,
>
> Indeed :)
>
>> so I really should do better than this.
>> Apologies, I'll pay closer attention in the future.
>
> Never mind, it's not a big deal. Emails with me CC'ed are highlighted
> in my mutt email client, therefore, it's unlikely I will miss them.
>
> --yliu
>
Sure. We all get too much email :)
- Panu -
next prev parent reply other threads:[~2016-02-18 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 9:47 Panu Matilainen
2016-02-18 13:25 ` Yuanhan Liu
2016-02-18 13:39 ` Panu Matilainen
2016-02-18 13:56 ` Yuanhan Liu
2016-02-18 14:07 ` Panu Matilainen [this message]
2016-02-19 1:56 ` Yuanhan Liu
2016-02-19 10:24 ` Thomas Monjalon
2016-02-23 15:34 ` Bruce Richardson
2016-02-18 19:26 ` 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=56C5D038.2070700@redhat.com \
--to=pmatilai@redhat.com \
--cc=dev@dpdk.org \
--cc=yuanhan.liu@linux.intel.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).