DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Jincheng Miao <jmiao@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] compatibility fallback and replacement of kernel function invoking
Date: Wed, 10 Dec 2014 03:58:33 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7D04D3@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1418182383-5744-1-git-send-email-jmiao@redhat.com>

Acked-by: Helin Zhang <helin.zhang@intel.com>

Note: Don't forget to add the version number to your patch name next time. E.g. [PATCH v3 0/4]

> -----Original Message-----
> From: Jincheng Miao [mailto:jmiao@redhat.com]
> Sent: Wednesday, December 10, 2014 11:33 AM
> To: dev@dpdk.org
> Cc: thomas.monjalon@6wind.com; Zhang, Helin; Jincheng Miao
> Subject: [PATCH 0/4] compatibility fallback and replacement of kernel function
> invoking
> 
> The related kernel function is:
> - pci_num_vf, it is introduced from upstream linux-2.6.34. For RHEL-based
> kernel, it is defined from RHEL5.9.
> 
> - kstrtoul, this function is united kernel API to replace strict_strtoul in the
> furture. It is introduced from linux-2.6.39. For RHEL6, it is defined from
> RHEL6.4.
> 
> This patchset do some compatiblity work for these two functions, and replace
> strict_strtoul which is depleted from linux-3.18.
> 
> v3:
>   Adjust pci_num_vf() introduced RHEL version number.
>   Seperate "replace strict_strtoul with kstrtoul" into 3 patches for igb_uio, kni,
> and xen_dom0. Add compat.h in kni and xen_dom0 for compatible with older
> kernels.
> 
> v2:
>   Merge these two patch in one patchset.
>   Compatible with old kernel for kstrtoul.
>   Compatible with RHEL6 for pci_num_vf.
> 
> Jincheng Miao (4):
>   igb_uio: compatible with upstream longterm kernel and RHEL
>   igb_uio: replace strict_strtoul with kstrtoul
>   kni: replace strict_strtoul with kstrtoul
>   xen_dom0: replace strict_strtoul with kstrtoul
> 
>  lib/librte_eal/linuxapp/igb_uio/compat.h        |   11 ++++++++++-
>  lib/librte_eal/linuxapp/igb_uio/igb_uio.c       |    4 ++--
>  lib/librte_eal/linuxapp/kni/compat.h            |   16
> ++++++++++++++++
>  lib/librte_eal/linuxapp/kni/kni_vhost.c         |    2 +-
>  lib/librte_eal/linuxapp/xen_dom0/compat.h       |   16
> ++++++++++++++++
>  lib/librte_eal/linuxapp/xen_dom0/dom0_mm_misc.c |    2 +-
>  6 files changed, 46 insertions(+), 5 deletions(-)  create mode 100644
> lib/librte_eal/linuxapp/kni/compat.h
>  create mode 100644 lib/librte_eal/linuxapp/xen_dom0/compat.h

  parent reply	other threads:[~2014-12-10  3:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  3:32 Jincheng Miao
2014-12-10  3:33 ` [dpdk-dev] [PATCH 1/4] igb_uio: compatible with upstream longterm kernel and RHEL Jincheng Miao
2014-12-10  3:33 ` [dpdk-dev] [PATCH 2/4] igb_uio: replace strict_strtoul with kstrtoul Jincheng Miao
2014-12-10  3:33 ` [dpdk-dev] [PATCH 3/4] kni: " Jincheng Miao
2014-12-10  8:39   ` Thomas Monjalon
2014-12-10  8:48     ` Jincheng Miao
2014-12-10  9:18       ` Thomas Monjalon
2014-12-10  9:39         ` Jincheng Miao
2014-12-10  3:33 ` [dpdk-dev] [PATCH 4/4] xen_dom0: " Jincheng Miao
2014-12-10  8:39   ` Thomas Monjalon
2014-12-10  3:58 ` Zhang, Helin [this message]
2014-12-10  4:15 ` [dpdk-dev] [PATCH 0/4] compatibility fallback and replacement of kernel function invoking Jincheng Miao

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A7D04D3@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jmiao@redhat.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).