public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
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 warnings after merge of the vfs-brauner tree
Date: Wed, 9 Oct 2024 17:29:38 +1100	[thread overview]
Message-ID: <20241009172938.05d5fae9@canb.auug.org.au> (raw)

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

Hi all,

After merging the vfs-brauner tree, today's linux-next build (htmldocs)
produced these warnings:

include/linux/fs.h:1071: warning: Function parameter or struct member 'f_ref' not described in 'file'
include/linux/fs.h:1071: warning: Excess struct member 'f_count' description in 'file'

Introduced by commit

  3488e37e1059 ("fs: port files to file_ref")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-10-09  6:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  6:29 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-11  3:37 linux-next: build warnings after merge of the vfs-brauner tree Stephen Rothwell
2024-12-19  6:31 ` Stephen Rothwell
2024-12-19 12:40   ` Jeff Layton
2024-12-19 20:36     ` Stephen Rothwell
2025-01-06 13:50       ` Geert Uytterhoeven
2024-12-13  4:27 Stephen Rothwell
2024-12-19  6:32 ` Stephen Rothwell
2025-01-14  5:48   ` Stephen Rothwell
2025-01-20  8:25     ` Stephen Rothwell
2025-01-20 12:15       ` Christian Brauner
2025-01-20 20:55         ` Stephen Rothwell
2025-03-05 10:07 Stephen Rothwell
2025-03-05 10:55 ` David Disseldorp
2025-07-17  7:36 Stephen Rothwell
2025-07-22 10:24 ` Jann Horn
2025-11-12  2:42 Stephen Rothwell
2025-11-12 10:10 ` Mateusz Guzik
2025-11-12 10:55   ` Stephen Rothwell
2025-11-12 10:57     ` Mateusz Guzik
2025-11-17  6:47 Stephen Rothwell
2025-12-16  0:52 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=20241009172938.05d5fae9@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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