From: Guillaume Nault <gnault@redhat.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org,
"Hideaki YOSHIFUJI" <yoshfuji@linux-ipv6.org>,
"David Ahern" <dsahern@kernel.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Russell Strong" <russell@strong.id.au>
Subject: Re: [PATCH net-next 0/4] inet: Separate DSCP from ECN bits using new dscp_t type
Date: Mon, 6 Dec 2021 20:57:38 +0100 [thread overview]
Message-ID: <20211206195738.GA7266@pc-4.home> (raw)
In-Reply-To: <cover.1638814614.git.gnault@redhat.com>
On Mon, Dec 06, 2021 at 07:22:02PM +0100, Guillaume Nault wrote:
> Following my talk at LPC 2021 [1], here's a patch series whose
> objective is to start fixing the problems with how DSCP and ECN bits
> are handled in the kernel.
This is of course an RFC patch series, not meant for merging. Sorry for
the missing RFC tag in the subject (used the wrong script :/).
next prev parent reply other threads:[~2021-12-06 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 18:22 [PATCH net-next 0/4] inet: Separate DSCP from ECN bits using new dscp_t type Guillaume Nault
2021-12-06 18:22 ` [PATCH net-next 1/4] ipv6: Define dscp_t and stop taking ECN bits into account in ip6-rules Guillaume Nault
2021-12-06 18:22 ` [PATCH net-next 2/4] ipv4: Stop taking ECN bits into account in ip4-rules Guillaume Nault
2021-12-06 18:22 ` [PATCH net-next 3/4] ipv4: Reject routes specifying ECN bits in rtm_tos Guillaume Nault
2021-12-06 18:22 ` [PATCH net-next 4/4] ipv4: Use dscp_t in struct fib_alias Guillaume Nault
2021-12-06 19:57 ` Guillaume Nault [this message]
2021-12-14 0:16 ` [PATCH net-next 0/4] inet: Separate DSCP from ECN bits using new dscp_t type Toke Høiland-Jørgensen
2021-12-15 16:48 ` Guillaume Nault
2021-12-15 20:40 ` Dave Taht
2021-12-17 17:55 ` Toke Høiland-Jørgensen
2021-12-17 22:52 ` Guillaume Nault
-- strict thread matches above, loose matches on Subject: below --
2022-02-04 13:58 Guillaume Nault
2022-02-07 6:08 ` David Ahern
2022-02-07 19:03 ` Toke Høiland-Jørgensen
2022-02-08 5:10 ` 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=20211206195738.GA7266@pc-4.home \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=russell@strong.id.au \
--cc=toke@redhat.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).