From: Guedes, Andre <andre.guedes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue PATCH v8 0/6] TSN: Add qdisc based config interface for CBS
Date: Mon, 16 Oct 2017 21:07:07 +0000 [thread overview]
Message-ID: <1508188025.5270.12.camel@intel.com> (raw)
In-Reply-To: <20171016.205146.1053238236578937188.davem@davemloft.net>
+Jeff
Since this patchset also touches the IGB driver, Jeff suggested we merged it
into his tree and he'd make a pull-request to your net-next tree.
@Jeff, are we moving with this approach or should David apply the patchset to
his net-next tree directly?
Thanks,
Andre
On Mon, 2017-10-16 at 20:51 +0100, David Miller wrote:
> I'm fine with this patch set.??I see it's against Jeff's next-queue, so
> where exactly do you want this to be merged???My net-next tree?
>
> Thank you.
next prev parent reply other threads:[~2017-10-16 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 0:25 [Intel-wired-lan] [next-queue PATCH v8 0/6] TSN: Add qdisc based config interface for CBS Vinicius Costa Gomes
2017-10-14 0:25 ` [Intel-wired-lan] [next-queue PATCH v8 1/6] net/sched: Check for null dev_queue on create flow Vinicius Costa Gomes
2017-10-14 0:25 ` [Intel-wired-lan] [next-queue PATCH v8 2/6] net/sched: Change behavior of mq select_queue() Vinicius Costa Gomes
2017-10-14 0:25 ` [Intel-wired-lan] [next-queue PATCH v8 3/6] net/sched: Add select_queue() class_ops for mqprio Vinicius Costa Gomes
2017-10-14 0:25 ` [Intel-wired-lan] [next-queue PATCH v8 4/6] net/sched: Introduce Credit Based Shaper (CBS) qdisc Vinicius Costa Gomes
2017-10-14 0:25 ` [Intel-wired-lan] [next-queue PATCH v8 5/6] net/sched: Add support for HW offloading for CBS Vinicius Costa Gomes
2017-10-14 0:25 ` [Intel-wired-lan] [next-queue PATCH v8 6/6] igb: Add support for CBS offload Vinicius Costa Gomes
2017-10-16 19:51 ` [Intel-wired-lan] [next-queue PATCH v8 0/6] TSN: Add qdisc based config interface for CBS David Miller
2017-10-16 21:07 ` Guedes, Andre [this message]
2017-10-16 22:20 ` Vinicius Costa Gomes
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=1508188025.5270.12.camel@intel.com \
--to=andre.guedes@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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