DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] virtio: Fix 2 compilation issues in virtio PMD
Date: Mon, 28 Jul 2014 07:35:52 +0000	[thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F96251180B281@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1406177865-9964-1-git-send-email-changchun.ouyang@intel.com>

Hi all,

> -----Original Message-----
> From: Ouyang, Changchun
> Sent: Thursday, July 24, 2014 12:58 PM
> To: dev@dpdk.org
> Cc: Cao, Waterman; Ouyang, Changchun
> Subject: [PATCH] virtio: Fix 2 compilation issues in virtio PMD
> 
> Fix 2 compilation issues in virtio PMD when dump option is enabled.
> 
> Signed-off-by: Changchun Ouyang <changchun.ouyang@intel.com>
> ---
>  lib/librte_pmd_virtio/virtio_ethdev.c | 2 +-
>  lib/librte_pmd_virtio/virtqueue.h     | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 

The offending commit which cause these 2 issues are:

commit f37cdfde46a30d93f3dd8a4e01243be8bc0ac142
Author: Stephen Hemminger <stephen@networkplumber.org>	
Date:   Fri Jun 13 18:06:23 2014 -0700
 
    virtio: remove unused virtqueue name
    
    vq_name is only used when setting up queue, and does not need
    to be saved.


commit ce65e697c67ba1a357d806eed05957b3d43f562c
Author: Stephen Hemminger <stephen@networkplumber.org>
Date:   Fri Jun 13 18:06:25 2014 -0700
 
    virtio: simplify the hardware structure
    
    The host_features are never used after negotiation.
    The PCI information is unused (and available in rte_pci if needed).

Thanks
Changchun

  reply	other threads:[~2014-07-28  7:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24  4:57 Ouyang Changchun
2014-07-28  7:35 ` Ouyang, Changchun [this message]
2014-08-01 14:36 ` 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=F52918179C57134FAEC9EA62FA2F96251180B281@shsmsx102.ccr.corp.intel.com \
    --to=changchun.ouyang@intel.com \
    --cc=dev@dpdk.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 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).