All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>, Andrii Nakryiko <andrii@kernel.org>
Cc: Eduard Zingerman <eddyz87@gmail.com>,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	netdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: linux-next: build failure after merge of the bfp-next tree
Date: Mon, 27 Apr 2026 15:26:02 +0200	[thread overview]
Message-ID: <20260427132604.3754048-2-thierry.reding@kernel.org> (raw)
In-Reply-To: <20260427132604.3754048-1-thierry.reding@kernel.org>

Hi all,

After merging the bfp-next tree, today's linux-next build (x86_64
allmodconfig ) failed like this:

    ERROR: modpost: "cnum64_umin" [drivers/net/ethernet/netronome/nfp/nfp.ko] undefined!
    ERROR: modpost: "cnum64_umax" [drivers/net/ethernet/netronome/nfp/nfp.ko] undefined!

Caused by commit

    b93f7180f0bc ("bpf: use accessor functions for bpf_reg_state min/max fields")

It looks like the issue here is that these new accessor functions are not
exported symbols and therefore can't be used by a driver that is built as
a module.

I've used the previous tree for today's linux-next.

Thanks,
Thierry

  reply	other threads:[~2026-04-27 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 13:26 linux-next: build failure after merge of the bpf-next tree Thierry Reding
2026-04-27 13:26 ` Thierry Reding [this message]
2026-04-27 13:45   ` linux-next: build failure after merge of the bfp-next tree Alan Maguire
2026-04-27 13:34 ` linux-next: build failure after merge of the bpf-next tree Thierry Reding
2026-04-27 13:43 ` Alan Maguire
2026-04-28 18:26 ` sashiko-bot

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=20260427132604.3754048-2-thierry.reding@kernel.org \
    --to=thierry.reding@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.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.