From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
mustafa.ismail@intel.com, shiraz.saleem@intel.com, jgg@ziepe.ca,
leon@kernel.org, mkalderon@marvell.com, aelior@marvell.com,
j.vosburgh@gmail.com, andy@greyhouse.net, dsahern@kernel.org,
kadlec@netfilter.org, roopa@nvidia.com, razor@blackwall.org
Subject: Re: [PATCH net-next] ipv4: Set scope explicitly in ip_route_output().
Date: Mon, 08 Apr 2024 12:21:42 +0000 [thread overview]
Message-ID: <171257890235.8472.12307217868929913978.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1f3c874fb825cdc030f729d2e48e6f45f3e3527f.1712347466.git.gnault@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 5 Apr 2024 22:05:00 +0200 you wrote:
> Add a "scope" parameter to ip_route_output() so that callers don't have
> to override the tos parameter with the RTO_ONLINK flag if they want a
> local scope.
>
> This will allow converting flowi4_tos to dscp_t in the future, thus
> allowing static analysers to flag invalid interactions between
> "tos" (the DSCP bits) and ECN.
>
> [...]
Here is the summary with links:
- [net-next] ipv4: Set scope explicitly in ip_route_output().
https://git.kernel.org/netdev/net-next/c/ec20b2830093
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-04-08 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 20:05 [PATCH net-next] ipv4: Set scope explicitly in ip_route_output() Guillaume Nault
2024-04-08 10:55 ` Leon Romanovsky
2024-04-08 12:21 ` patchwork-bot+netdevbpf [this message]
2024-04-11 9:36 ` Hangbin Liu
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=171257890235.8472.12307217868929913978.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aelior@marvell.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=j.vosburgh@gmail.com \
--cc=jgg@ziepe.ca \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=mkalderon@marvell.com \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=shiraz.saleem@intel.com \
/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).