From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>, dev <dev@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: set git tree for packet framework and QoS
Date: Tue, 14 Jan 2020 11:46:23 +0100 [thread overview]
Message-ID: <CAJFAV8x639O0t-pxxnv0P_UR4aFCQX6Sh1G+dpXVgzm8P_11bg@mail.gmail.com> (raw)
In-Reply-To: <3216938.qSoW2BAyJ8@xps>
On Tue, Jan 14, 2020 at 11:36 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 14/01/2020 11:27, David Marchand:
> > On Tue, Jan 14, 2020 at 11:23 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> > > 14/01/2020 11:05, David Marchand:
> > > About ethdev TM and MTR, I am not sure what is the right thing to do.
> >
> > The drivers using those apis are in dpdk-next-net.
>
> Yes this is my question:
> Is it fine merging QoS related patches on ethdev, drivers and testpmd
> in dpdk-next-net, or do we want them to be managed separately in dpdk-next-qos?
> There is not much activity here, so I am just anticipating a heavier activity.
If we move those files under the qos subtree, it will be impossible
(?) to identify QoS only changes on those drivers, so we will end with
the patches going to master.
--
David Marchand
next prev parent reply other threads:[~2020-01-14 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 10:05 David Marchand
2020-01-14 10:23 ` Thomas Monjalon
2020-01-14 10:27 ` David Marchand
2020-01-14 10:34 ` Dumitrescu, Cristian
2020-01-14 10:36 ` Thomas Monjalon
2020-01-14 10:46 ` David Marchand [this message]
2020-01-14 13:09 ` [dpdk-dev] [PATCH v2] " David Marchand
2020-01-22 21:45 ` 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=CAJFAV8x639O0t-pxxnv0P_UR4aFCQX6Sh1G+dpXVgzm8P_11bg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.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).