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, autofs@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Ian Kent <raven@themaw.net>
Subject: Re: [PATCH] fs: autofs: add MODULE_DESCRIPTION()
Date: Tue, 28 May 2024 19:03:46 +0100 [thread overview]
Message-ID: <20240528180346.GG2118490@ZenIV> (raw)
In-Reply-To: <20240528-ausnimmt-leise-4feb91054db2@brauner>
On Tue, May 28, 2024 at 01:39:03PM +0200, Christian Brauner wrote:
> On Mon, 27 May 2024 12:22:16 -0700, Jeff Johnson wrote:
> > Fix the 'make W=1' warning:
> > WARNING: modpost: missing MODULE_DESCRIPTION() in fs/autofs/autofs4.o
> >
> >
>
> Applied to the v6.10-rc1 branch of the vfs/vfs.git tree.
> Patches in the v6.10-rc1 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: v6.10-rc1
*Ugh*
Free advice: avoid mixing tag and branch names. git tries to do the
right thing when it runs into ambiguities, but it's really asking for
headache.
next prev parent reply other threads:[~2024-05-28 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 19:22 [PATCH] fs: autofs: add MODULE_DESCRIPTION() Jeff Johnson
2024-05-28 10:09 ` Christian Brauner
2024-05-28 11:39 ` Christian Brauner
2024-05-28 18:03 ` Al Viro [this message]
2024-05-29 7:45 ` Christian Brauner
2024-05-29 0:48 ` Ian Kent
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=20240528180346.GG2118490@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=autofs@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=raven@themaw.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.