From: Christian Brauner <brauner@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Amir Goldstein <amir73il@gmail.com>, NeilBrown <neil@brown.name>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>
Subject: Re: (subset) [PATCH 01/10] exportfs: add module description
Date: Tue, 25 Mar 2025 15:58:29 +0100 [thread overview]
Message-ID: <20250325-typisch-absicht-8fd692d68fe6@brauner> (raw)
In-Reply-To: <20250324173242.1501003-1-arnd@kernel.org>
On Mon, 24 Mar 2025 18:32:26 +0100, Arnd Bergmann wrote:
> Every loadable module should have a description, to avoid a warning such as:
>
> WARNING: modpost: missing MODULE_DESCRIPTION() in fs/exportfs/exportfs.o
>
>
I've removed mentioning of NFS from the module description because
exportfs is now used for a lot more.
---
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[01/10] exportfs: add module description
https://git.kernel.org/vfs/vfs/c/e3206c4aa06f
prev parent reply other threads:[~2025-03-25 14:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:32 [PATCH 01/10] exportfs: add module description Arnd Bergmann
2025-03-24 17:32 ` [PATCH 02/10] ASN.1: " Arnd Bergmann
2025-04-06 18:21 ` Geert Uytterhoeven
2025-03-24 17:32 ` [PATCH 03/10] samples/livepatch: add module descriptions Arnd Bergmann
2025-03-25 10:01 ` Petr Mladek
2025-03-25 15:03 ` Jeff Johnson
2025-03-24 17:32 ` [PATCH 04/10] fpga: tests: " Arnd Bergmann
2025-03-25 17:06 ` Marco Pagani
2025-04-25 4:27 ` Xu Yilun
2025-03-24 17:32 ` [PATCH 05/10] xenbus: add module description Arnd Bergmann
2025-03-27 16:43 ` Jürgen Groß
2025-03-24 17:32 ` [PATCH 06/10] zlib: " Arnd Bergmann
2025-03-24 17:32 ` [PATCH 07/10] ucs2_string: " Arnd Bergmann
2025-03-24 17:32 ` [PATCH 08/10] kunit: add module description for backtrace suppression test Arnd Bergmann
2025-03-24 17:32 ` [PATCH 09/10] mm/kasan: add module decription Arnd Bergmann
2025-03-24 22:00 ` Andrey Konovalov
2025-03-24 17:32 ` [PATCH 10/10] kunit: slub: add module description Arnd Bergmann
2025-03-25 14:58 ` Christian Brauner [this message]
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=20250325-typisch-absicht-8fd692d68fe6@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=neil@brown.name \
--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