public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 25 Apr 2023 15:55:11 +0300	[thread overview]
Message-ID: <20230425125511.qro3vql5aivxnxlh@skbuf> (raw)
In-Reply-To: <5575810d-ceee-7b7b-fba4-e14e5ca6e412@kernel.org>

On Mon, Apr 24, 2023 at 07:47:31PM -0600, David Ahern wrote:
> On 4/22/23 10:59 AM, Vladimir Oltean wrote:
> > 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?
> 
> iproute2 follows the netdev dev model with a main tree for bug fixes and
> -next tree for features. In the future please separate out the patches
> and send with proper targets. If a merge is needed you can state that in
> the cover letter of the set for -next.

I know that the trees are split and it is no coincidence that my patches
were sorted in the correct order. I've been working for 10 months on
this small feature and I was impatient to get it over with, so I wanted
to eliminate one round-trip time if possible (send to "iproute2", ask
for merge, send to "iproute2-next"). I requested this honestly thinking
that there would be no difference to the end result, only less pretentious
in terms of the process. If there is any automation (I didn't see any in
Patchwork at least) or any other reason that would justify the more
pretentious process, then again, my excuses, I plead ignorance and I
will follow it more strictly next time, but I'd also like to know it :)

  reply	other threads:[~2023-04-25 12:55 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
2023-04-25  1:47     ` David Ahern
2023-04-25 12:55       ` Vladimir Oltean [this message]
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=20230425125511.qro3vql5aivxnxlh@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