netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	aaron.young@oracle.com, rashmi.narasimhan@oracle.com
Subject: Re: [PATCH net] net: sun: SUNVNET_COMMON should depend on INET
Date: Tue, 28 Sep 2021 12:30:08 +0000	[thread overview]
Message-ID: <163283220814.6805.7628425135389205973.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210927214823.13683-1-rdunlap@infradead.org>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Mon, 27 Sep 2021 14:48:23 -0700 you wrote:
> When CONFIG_INET is not set, there are failing references to IPv4
> functions, so make this driver depend on INET.
> 
> Fixes these build errors:
> 
> sparc64-linux-ld: drivers/net/ethernet/sun/sunvnet_common.o: in function `sunvnet_start_xmit_common':
> sunvnet_common.c:(.text+0x1a68): undefined reference to `__icmp_send'
> sparc64-linux-ld: drivers/net/ethernet/sun/sunvnet_common.o: in function `sunvnet_poll_common':
> sunvnet_common.c:(.text+0x358c): undefined reference to `ip_send_check'
> 
> [...]

Here is the summary with links:
  - [net] net: sun: SUNVNET_COMMON should depend on INET
    https://git.kernel.org/netdev/net/c/103bde372f08

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



      reply	other threads:[~2021-09-28 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 21:48 [PATCH net] net: sun: SUNVNET_COMMON should depend on INET Randy Dunlap
2021-09-28 12:30 ` 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=163283220814.6805.7628425135389205973.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aaron.young@oracle.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rashmi.narasimhan@oracle.com \
    --cc=rdunlap@infradead.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).