From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Neal Cardwell <ncardwell@google.com>,
Simon Horman <horms@kernel.org>, Ido Schimmel <idosch@nvidia.com>,
David Ahern <dsahern@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 1/3] net: constify sk_skb_reason_drop() sock parameter
Date: Fri, 8 May 2026 15:15:23 -0700 [thread overview]
Message-ID: <20260508151523.609cadaa@kernel.org> (raw)
In-Reply-To: <20260507084305.2506115-2-edumazet@google.com>
On Thu, 7 May 2026 08:43:03 +0000 Eric Dumazet wrote:
> TP_PROTO(struct sk_buff *skb, void *location,
> - enum skb_drop_reason reason, struct sock *rx_sk),
> + enum skb_drop_reason reason, const struct sock *rx_sk),
build says drop_monitor registers for this tracepoint from within
the kernel, and needs adjusting.
next prev parent reply other threads:[~2026-05-08 22:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 8:43 [PATCH net-next 0/3] net: use IP_OUTNOROUTES drop reason Eric Dumazet
2026-05-07 8:43 ` [PATCH net-next 1/3] net: constify sk_skb_reason_drop() sock parameter Eric Dumazet
2026-05-07 15:14 ` David Ahern
2026-05-07 22:43 ` Kuniyuki Iwashima
2026-05-08 22:15 ` Jakub Kicinski [this message]
2026-05-11 7:16 ` Eric Dumazet
2026-05-07 8:43 ` [PATCH net-next 2/3] tcp: use SKB_DROP_REASON_IP_OUTNOROUTES in tcp_v6_send_response() Eric Dumazet
2026-05-07 15:14 ` David Ahern
2026-05-07 22:56 ` Kuniyuki Iwashima
2026-05-07 8:43 ` [PATCH net-next 3/3] ipv6: use SKB_DROP_REASON_IP_OUTNOROUTES in inet6_csk_xmit() Eric Dumazet
2026-05-07 15:14 ` David Ahern
2026-05-07 22:56 ` Kuniyuki Iwashima
2026-05-11 7:13 ` [PATCH net-next 0/3] net: use IP_OUTNOROUTES drop reason Eric Dumazet
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=20260508151523.609cadaa@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.