public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: 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 vfs-brauner-fixes tree
Date: Thu, 9 Apr 2026 13:17:08 +0100	[thread overview]
Message-ID: <adeYxPwylSYTR7by@sirena.org.uk> (raw)

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

Hi all,

After merging the vfs-brauner-fixes tree, today's linux-next build
(arm64 allnoconfig) failed like this:

/tmp/next/build/fs/sysfs/mount.c: In function 'sysfs_init_fs_context':
/tmp/next/build/fs/sysfs/mount.c:75:37: error: implicit declaration of function 'to_net_ns'; did you mean
'get_net_ns'? [-Wimplicit-function-declaration]
   75 |                 struct net *netns = to_net_ns(ns);
      |                                     ^~~~~~~~~ get_net_ns
/tmp/next/build/fs/sysfs/mount.c:75:37: error: initialization of 'struct net *' from 'int' makes pointer from integer without a cast [-Wint-conversion]

Caused by commit

  9a8098b1d5023 (kernfs: pass struct ns_common instead of const void * for namespace tags)

There's a missing include of net/net_namespace.h.  I have used the
version from next-20260408 instead.

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

             reply	other threads:[~2026-04-09 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 12:17 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17  1:46 linux-next: build failure after merge of the vfs-brauner-fixes tree Stephen Rothwell

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=adeYxPwylSYTR7by@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox