From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v2 iproute2-next 00/10] Add tc-mqprio and tc-taprio support for preemptible traffic classes
Date: Sat, 22 Apr 2023 19:59:45 +0300 [thread overview]
Message-ID: <20230422165945.7df2xbpeg3llgt7x@skbuf> (raw)
In-Reply-To: <535c37f2-df90-ae4b-5b5a-8bf75916ad22@kernel.org>
On Sat, Apr 22, 2023 at 10:14:01AM -0600, David Ahern wrote:
> Thanks for updating the man pages. These should go through main first; I
> can sync to main after those are applied and before your set if needed.
>
> ... and updated headers.
>
> Repost the patches as 2 sets with the man page fixes targeted at main
> and the new preemptible work for -next.
So the status is as follows: patches 01-06 apply cleanly to the current
iproute2/main, and after another iproute2 -> iproute2-next merge, patch
07 can be skipped and patches 08-10 also apply cleanly to the resulting
iproute2-next branch.
Unless there are changes I need to make to the contents of the patches,
could you take these from the lists, or is that a no-no?
next prev parent reply other threads:[~2023-04-22 16:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 11:39 [PATCH v2 iproute2-next 00/10] Add tc-mqprio and tc-taprio support for preemptible traffic classes Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 01/10] tc/taprio: add max-sdu to the man page SYNOPSIS section Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 02/10] tc/taprio: add a size table to the examples from the man page Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 03/10] tc/mqprio: fix stray ] in man page synopsis Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 04/10] tc/mqprio: use words in man page to express min_rate/max_rate dependency on bw_rlimit Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 05/10] tc/mqprio: break up synopsis into multiple lines Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 06/10] tc/taprio: break up help text " Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 07/10] Update kernel headers Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 08/10] utils: add max() definition Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 09/10] tc/mqprio: add support for preemptible traffic classes Vladimir Oltean
2023-04-30 0:42 ` Stephen Hemminger
2023-04-30 1:33 ` Vladimir Oltean
2023-04-18 11:39 ` [PATCH v2 iproute2-next 10/10] tc/taprio: " Vladimir Oltean
2023-04-22 16:14 ` [PATCH v2 iproute2-next 00/10] Add tc-mqprio and tc-taprio " David Ahern
2023-04-22 16:59 ` Vladimir Oltean [this message]
2023-04-25 1:47 ` David Ahern
2023-04-25 12:55 ` Vladimir Oltean
2023-04-26 0:42 ` David Ahern
2023-04-24 16:40 ` patchwork-bot+netdevbpf
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=20230422165945.7df2xbpeg3llgt7x@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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