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, dsahern@kernel.org,
horms@verge.net.au, ja@ssi.bg, pablo@netfilter.org,
kadlec@netfilter.org, fw@strlen.de, marcelo.leitner@gmail.com,
lucien.xin@gmail.com
Subject: Re: [PATCH net-next] ipv4: Drop tos parameter from flowi4_update_output()
Date: Fri, 02 Jun 2023 10:00:19 +0000 [thread overview]
Message-ID: <168570001969.17073.4452978864455433117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <f9e28cf551d9efb9278ac80d34d458295d8c845a.1685637136.git.gnault@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 1 Jun 2023 18:37:46 +0200 you wrote:
> Callers of flowi4_update_output() never try to update ->flowi4_tos:
>
> * ip_route_connect() updates ->flowi4_tos with its own current
> value.
>
> * ip_route_newports() has two users: tcp_v4_connect() and
> dccp_v4_connect. Both initialise fl4 with ip_route_connect(), which
> in turn sets ->flowi4_tos with RT_TOS(inet_sk(sk)->tos) and
> ->flowi4_scope based on SOCK_LOCALROUTE.
>
> [...]
Here is the summary with links:
- [net-next] ipv4: Drop tos parameter from flowi4_update_output()
https://git.kernel.org/netdev/net-next/c/3f06760c00f5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-02 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 16:37 [PATCH net-next] ipv4: Drop tos parameter from flowi4_update_output() Guillaume Nault
2023-06-02 10:00 ` patchwork-bot+netdevbpf [this message]
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=168570001969.17073.4452978864455433117.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gnault@redhat.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.