mbox series

[v2,0/2] Split driver specific commands out of testpmd

Message ID 20220524200642.1322115-1-david.marchand@redhat.com (mailing list archive)
Headers
Series Split driver specific commands out of testpmd |

Message

David Marchand May 24, 2022, 8:06 p.m. UTC 
  Hello,

Following TB decision [1] and recent discussions on the driver specific
commands in testpmd, here is a proposal on how the split could be done.

For now, this series simply moves the testpmd code in the driver
directory. The driver specific testpmd code is still compiled as part of
testpmd compilation via a global meson testpmd_driver_sources list.

1: https://mails.dpdk.org/archives/dev/2022-April/239191.html

Comments

Andrew Rybchenko May 31, 2022, 3:18 p.m. UTC | #1 
On 5/24/22 23:06, David Marchand wrote:
> Hello,
> 
> Following TB decision [1] and recent discussions on the driver specific
> commands in testpmd, here is a proposal on how the split could be done.
> 
> For now, this series simply moves the testpmd code in the driver
> directory. The driver specific testpmd code is still compiled as part of
> testpmd compilation via a global meson testpmd_driver_sources list.
> 
> 1: https://mails.dpdk.org/archives/dev/2022-April/239191.html
> 

Applied to dpdk-next-net/main, thanks.