public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Steffen Klassert <steffen.klassert@secunet•com>
Cc: Eric Dumazet <edumazet@google•com>,
	Jakub Kicinski <kuba@kernel•org>,
	Willem de Bruijn <willemb@google•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the ipsec-next tree
Date: Mon, 26 Jan 2026 17:33:22 +0000	[thread overview]
Message-ID: <aXelYpP4MFOuc4vY@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 814 bytes --]

Hi all,

After merging the ipsec-next tree, today's linux-next build (arm64
defconfig) failed like this:

/tmp/next/build/net/core/sysctl_net_core.c: In function 'proc_do_rss_key':
/tmp/next/build/net/core/sysctl_net_core.c:333:23: error: implicit declaration of function 'hex_byte_pack' [-Wimplicit-function-declaration]
  333 |                 pos = hex_byte_pack(pos, netdev_rss_key[i]);
      |                       ^~~~~~~~~~~~~
/tmp/next/build/net/core/sysctl_net_core.c:333:21: error: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
  333 |                 pos = hex_byte_pack(pos, netdev_rss_key[i]);
      |                     ^

Caused by commit

   37b0ea8fef56c (net: expand NETDEV_RSS_KEY_LEN to 256 bytes)

I have used the tree from 20260123 instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-01-26 17:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aXelYpP4MFOuc4vY@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=steffen.klassert@secunet$(echo .)com \
    --cc=willemb@google$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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