DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ravi Kerur <rkerur@gmail.com>, dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH v8 6/6] Move common functions in eal_pci.c
Date: Tue, 18 Dec 2018 01:47:15 +0000	[thread overview]
Message-ID: <452bc222-ae4e-0dab-08ae-13d2b93a6201@intel.com> (raw)
In-Reply-To: <1430264809-32599-6-git-send-email-rkerur@gmail.com>

On 4/29/2015 12:46 AM, rkerur at gmail.com (Ravi Kerur) wrote:
> Changes in v8
> None
> 
> Changes in v7
> Rebase to latest code.
> 
> Changes in v6
> Split changes due to complexity. v6 includes moving
> rte_eal_pci_probe_one_driver function and its associated
> utility functions only.
> 
> Changes in v5
> Rebase to latest code.
> Removed RTE_EXEC_ENV_BSDAPP from earlier changes.
> 
> Changes in v4
> Move common functions in eal_pci.c to librte_eal/common/
> eal_common_pci.c file.
> 
> Following functions are moved to eal_common_pci.c file.
> 
> void *pci_map_resource(void *requested_addr, const int vfio_fd,
>       const char *devname, off_t offset, size_t size);
> int pci_addr_comparison(struct rte_pci_addr *addr,
>                         struct rte_pci_addr *addr2);
> int rte_eal_pci_probe_one_driver(struct rte_pci_driver *dr,
>                         struct rte_pci_device *dev);
> 
> Use RTE_EXEC_ENV_BSDAPP to differentiate minor differences in
> common function.
> Fix checkpatch warnings and errors.
> 
> Changes in v3
> N/A
> 
> Changes in v2
> N/A
> 
> Changes in v1
> N/A
> 
> Signed-off-by: Ravi Kerur <rkerur at gmail.com>

Same for this one, updated as rejected because of timeout, like other if
it is still relevant please let us know.

Sorry for any inconvenience caused.

Mentioned patch: https://patches.dpdk.org/patch/4491/

  reply	other threads:[~2018-12-18  1:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 23:46 [dpdk-dev] [PATCH v8 0/6] Move common functions in EAL Ravi Kerur
2015-04-28 23:46 ` [dpdk-dev] [PATCH v8 1/6] Move common functions in eal_thread.c Ravi Kerur
2015-04-28 23:46   ` [dpdk-dev] [PATCH v8 2/6] Move common functions in eal.c Ravi Kerur
2018-12-18  1:42     ` Ferruh Yigit
2018-12-18  1:43       ` Ferruh Yigit
2015-04-28 23:46   ` [dpdk-dev] [PATCH v8 3/6] Move common functions in eal_lcore.c Ravi Kerur
2015-04-28 23:46   ` [dpdk-dev] [PATCH v8 4/6] Move common functions in eal_timer.c Ravi Kerur
2015-04-28 23:46   ` [dpdk-dev] [PATCH v8 5/6] Move common functions in eal_memory.c Ravi Kerur
2015-04-28 23:46   ` [dpdk-dev] [PATCH v8 6/6] Move common functions in eal_pci.c Ravi Kerur
2018-12-18  1:47     ` Ferruh Yigit [this message]
2015-04-29 10:14 ` [dpdk-dev] [PATCH v8 0/6] Move common functions in EAL Neil Horman

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=452bc222-ae4e-0dab-08ae-13d2b93a6201@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.com \
    --cc=rkerur@gmail.com \
    --cc=thomas@monjalon.net \
    /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).