From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/2] prepare function names for bus move
Date: Thu, 4 May 2017 09:40:11 -0700 [thread overview]
Message-ID: <20170504094011.32cfe064@xeon-e3> (raw)
In-Reply-To: <20170504161851.26574-1-thomas@monjalon.net>
On Thu, 4 May 2017 18:18:49 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> It is planned to move the bus PCI and VDEV to /drivers/bus/
> during 17.08. So the eal_ prefix will not make sense.
> Let's rename now before releasing 17.05 where EAL API has
> already some breaking changes.
>
> Thomas Monjalon (2):
> pci: remove eal prefix
> vdev: remove eal prefix
>
> app/test-pmd/testpmd.c | 2 +-
> doc/guides/cryptodevs/aesni_gcm.rst | 4 +-
> doc/guides/cryptodevs/aesni_mb.rst | 4 +-
> doc/guides/cryptodevs/kasumi.rst | 4 +-
> doc/guides/cryptodevs/null.rst | 4 +-
> doc/guides/cryptodevs/scheduler.rst | 4 +-
> doc/guides/cryptodevs/snow3g.rst | 4 +-
> doc/guides/cryptodevs/zuc.rst | 4 +-
> doc/guides/eventdevs/octeontx.rst | 4 +-
> doc/guides/eventdevs/sw.rst | 4 +-
> doc/guides/prog_guide/cryptodev_lib.rst | 4 +-
> .../sample_app_ug/l2_forward_real_virtual.rst | 4 +-
> doc/guides/sample_app_ug/link_status_intr.rst | 4 +-
> doc/guides/sample_app_ug/multi_process.rst | 2 +-
> doc/guides/sample_app_ug/netmap_compatibility.rst | 2 +-
> doc/guides/sample_app_ug/quota_watermark.rst | 4 +-
> drivers/net/bnx2x/bnx2x.h | 6 +-
> drivers/net/bonding/rte_eth_bond_api.c | 4 +-
> drivers/net/cxgbe/base/adapter.h | 10 +--
> drivers/net/i40e/i40e_ethdev.c | 6 +-
> drivers/net/mlx4/mlx4.c | 2 +-
> drivers/net/mlx5/mlx5.c | 2 +-
> drivers/net/virtio/virtio_ethdev.c | 10 +--
> drivers/net/virtio/virtio_pci.c | 81 ++++++++++------------
> drivers/net/virtio/virtio_user_ethdev.c | 2 +-
> lib/librte_cryptodev/rte_cryptodev.c | 6 +-
> lib/librte_eal/bsdapp/eal/eal_pci.c | 40 +++++------
> lib/librte_eal/bsdapp/eal/rte_eal_version.map | 38 +++++-----
> lib/librte_eal/common/eal_common_dev.c | 8 +--
> lib/librte_eal/common/eal_common_pci.c | 42 +++++------
> lib/librte_eal/common/eal_common_vdev.c | 8 +--
> lib/librte_eal/common/eal_private.h | 8 +--
> lib/librte_eal/common/include/rte_dev.h | 4 +-
> lib/librte_eal/common/include/rte_pci.h | 46 ++++++------
> lib/librte_eal/common/include/rte_vdev.h | 6 +-
> lib/librte_eal/linuxapp/eal/eal_pci.c | 38 +++++-----
> lib/librte_eal/linuxapp/eal/rte_eal_version.map | 38 +++++-----
> lib/librte_eventdev/rte_eventdev.c | 4 +-
> test/test/test_cryptodev.c | 20 +++---
> test/test/test_cryptodev_perf.c | 10 +--
> test/test/test_eventdev.c | 2 +-
> test/test/test_eventdev_octeontx.c | 2 +-
> test/test/test_eventdev_sw.c | 2 +-
> test/test/test_link_bonding_rssconf.c | 2 +-
> 44 files changed, 250 insertions(+), 255 deletions(-)
>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2017-05-04 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 16:18 [PATCH 0/2] prepare function names for bus move Thomas Monjalon
2017-05-04 16:18 ` [PATCH 1/2] pci: remove eal prefix Thomas Monjalon
2017-05-04 16:18 ` [PATCH 2/2] vdev: " Thomas Monjalon
2017-05-04 16:40 ` Stephen Hemminger [this message]
2017-05-05 12:41 ` [PATCH 0/2] prepare function names for bus move 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=20170504094011.32cfe064@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--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 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.