From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, David Marchand <david.marchand@6wind.com>,
Helin Zhang <helin.zhang@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: Re: [dpdk-dev] [PATCH 3/3] eal: remove rte_pci_dev_ids.h
Date: Sat, 06 Aug 2016 14:55:57 +0200 [thread overview]
Message-ID: <2065608.RmlMMznbWI@xps13> (raw)
In-Reply-To: <1470406171-24754-4-git-send-email-ferruh.yigit@intel.com>
2016-08-05 15:09, Ferruh Yigit:
> All PCI device ids moved to drivers, it is safe to delete
> rte_pci_dev_ids.h
Good move. Thanks Ferruh!
> --- a/doc/guides/prog_guide/dev_kit_build_system.rst
> +++ b/doc/guides/prog_guide/dev_kit_build_system.rst
> @@ -93,20 +93,20 @@ Each build directory contains include files, libraries, and applications:
> cmdline_cirbuf.h rte_cycles.h rte_memory.h
> cmdline.h rte_debug.h rte_mempool.h
> cmdline_parse_etheraddr.h rte_eal.h rte_memzone.h
> - cmdline_parse.h rte_errno.h rte_pci_dev_ids.h
> - cmdline_parse_ipaddr.h rte_ethdev.h rte_pci.h
> - cmdline_parse_num.h rte_ether.h rte_per_lcore.h
> - cmdline_parse_portlist.h rte_fbk_hash.h rte_prefetch.h
> - cmdline_parse_string.h rte_hash_crc.h rte_random.h
> - cmdline_rdline.h rte_hash.h rte_ring.h
> - cmdline_socket.h rte_interrupts.h rte_rwlock.h
> - cmdline_vt100.h rte_ip.h rte_sctp.h
> - exec-env rte_jhash.h rte_spinlock.h
> - rte_alarm.h rte_launch.h rte_string_fns.h
> - rte_atomic.h rte_lcore.h rte_tailq.h
> - rte_branch_prediction.h rte_log.h rte_tcp.h
> - rte_byteorder.h rte_lpm.h rte_timer.h
> - rte_common.h rte_malloc.h rte_udp.h
> + cmdline_parse.h rte_errno.h rte_pci.h
> + cmdline_parse_ipaddr.h rte_ethdev.h rte_per_lcore.h
> + cmdline_parse_num.h rte_ether.h rte_prefetch.h
> + cmdline_parse_portlist.h rte_fbk_hash.h rte_random.h
> + cmdline_parse_string.h rte_hash_crc.h rte_ring.h
> + cmdline_rdline.h rte_hash.h rte_rwlock.h
> + cmdline_socket.h rte_interrupts.h rte_sctp.h
> + cmdline_vt100.h rte_ip.h rte_spinlock.h
> + exec-env rte_jhash.h rte_string_fns.h
> + rte_alarm.h rte_launch.h rte_tailq.h
> + rte_atomic.h rte_lcore.h rte_tcp.h
> + rte_branch_prediction.h rte_log.h rte_timer.h
> + rte_byteorder.h rte_lpm.h rte_udp.h
> + rte_common.h rte_malloc.h
> rte_config.h rte_mbuf.h
What do you think about this list? I would say we can remove it.
next prev parent reply other threads:[~2016-08-06 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 14:09 [dpdk-dev] [PATCH 0/3] " Ferruh Yigit
2016-08-05 14:09 ` [dpdk-dev] [PATCH 1/3] net/ixgbe: move PCI device ids to the driver Ferruh Yigit
2016-08-08 6:36 ` David Marchand
2016-08-08 9:10 ` Ferruh Yigit
2016-08-10 12:07 ` David Marchand
2016-08-05 14:09 ` [dpdk-dev] [PATCH 2/3] net/igb: " Ferruh Yigit
2016-08-05 14:09 ` [dpdk-dev] [PATCH 3/3] eal: remove rte_pci_dev_ids.h Ferruh Yigit
2016-08-06 12:55 ` Thomas Monjalon [this message]
2016-08-08 6:20 ` David Marchand
2016-08-23 13:35 ` Thomas Monjalon
2016-08-23 13:37 ` [dpdk-dev] [PATCH 0/3] " 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=2065608.RmlMMznbWI@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=wenzhuo.lu@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).