All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org, eric.dumazet@gmail.com,
	lkp@intel.com
Subject: Re: [PATCH net-next] net: always declare __sock_wfree() and tcp_wfree()
Date: Sat, 16 May 2026 01:00:09 +0000	[thread overview]
Message-ID: <177889320974.213149.14979422206734256162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260514095506.3919094-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 14 May 2026 09:55:06 +0000 you wrote:
> Even if guarded by IS_ENABLED(CONFIG_INET) compilers need to know
> what __sock_wfree() and tcp_wfree() are:
> 
>    include/net/sock.h:1861:63: note: each undeclared identifier is reported only once for each function it appears in
>    include/net/sock.h:1862:63: error: 'tcp_wfree' undeclared (first use in this function); did you mean 'sock_wfree'?
>     1862 |                (IS_ENABLED(CONFIG_INET) && skb->destructor == tcp_wfree);
> 
> [...]

Here is the summary with links:
  - [net-next] net: always declare __sock_wfree() and tcp_wfree()
    https://git.kernel.org/netdev/net-next/c/e758acedce4e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-05-16  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14  9:55 [PATCH net-next] net: always declare __sock_wfree() and tcp_wfree() Eric Dumazet
2026-05-16  1: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=177889320974.213149.14979422206734256162.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lkp@intel.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.