From: Al Viro <viro@zeniv.linux.org.uk>
To: Christian Brauner <brauner@kernel.org>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] fs/adfs: add MODULE_DESCRIPTION
Date: Mon, 27 May 2024 17:40:22 +0100 [thread overview]
Message-ID: <20240527164022.GE2118490@ZenIV> (raw)
In-Reply-To: <20240524-zumal-butterbrot-015b2a21efd5@brauner>
On Fri, May 24, 2024 at 03:13:04PM +0200, Christian Brauner wrote:
> On Thu, 23 May 2024 06:58:01 -0700, Jeff Johnson wrote:
> > Fix the 'make W=1' issue:
> > WARNING: modpost: missing MODULE_DESCRIPTION() in fs/adfs/adfs.o
> >
> >
>
> Sure, why not.
Might make sense to move those into a separate branch, IMO (and feel
free to slap ACKed-by: Al Viro <viro@zeniv.linux.org.uk> on those -
AFAICS all of them look reasonable).
next prev parent reply other threads:[~2024-05-27 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 13:58 [PATCH] fs/adfs: add MODULE_DESCRIPTION Jeff Johnson
2024-05-24 13:13 ` Christian Brauner
2024-05-27 16:40 ` Al Viro [this message]
2024-05-28 10:00 ` Christian Brauner
2024-07-11 17:35 ` Jeff Johnson
2024-07-15 11:48 ` Christian Brauner
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=20240527164022.GE2118490@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
/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