From: Christian Brauner <brauner@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jeff Layton <jlayton@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the vfs-brauner tree
Date: Wed, 24 May 2023 11:06:39 +0200 [thread overview]
Message-ID: <20230524-golfball-bittsteller-7cd8e9a75fe8@brauner> (raw)
In-Reply-To: <20230524134623.733082d7@canb.auug.org.au>
On Wed, May 24, 2023 at 01:46:23PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the vfs-brauner tree, today's linux-next build (htmldocs)
> produced this warning:
>
> fs/stat.c:80: warning: Function parameter or member 'request_mask' not described in 'generic_fillattr'
>
> Introduced by commit
>
> 8fb690f6de31 ("fs: pass the request_mask to generic_fillattr")
Thanks, Jeff will send a new version of the series which should fix
this hopefully.
next prev parent reply other threads:[~2023-05-24 9:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 3:46 linux-next: build warning after merge of the vfs-brauner tree Stephen Rothwell
2023-05-24 9:06 ` Christian Brauner [this message]
2023-07-04 3:51 Stephen Rothwell
2023-07-31 3:58 Stephen Rothwell
2023-08-07 5:38 Stephen Rothwell
2023-08-15 11:15 Stephen Rothwell
2023-09-25 4:31 Stephen Rothwell
2023-11-24 2:13 Stephen Rothwell
2023-11-24 7:58 ` Amir Goldstein
2023-12-21 7:48 Stephen Rothwell
2023-12-21 13:19 ` David Howells
2024-01-17 2:39 Stephen Rothwell
2024-03-05 23:51 Stephen Rothwell
2024-03-06 2:48 ` Linus Torvalds
2024-03-06 4:37 ` Stephen Rothwell
2024-03-06 4:47 ` Linus Torvalds
2024-03-06 9:55 ` Christian Brauner
2024-03-06 4:58 ` 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=20230524-golfball-bittsteller-7cd8e9a75fe8@brauner \
--to=brauner@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).