From: Dan Carpenter <dan.carpenter@oracle.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Wei Yongjun <weiyongjun1@huawei.com>, Neil Brown <neilb@suse.de>,
Bruce Fields <bfields@fieldses.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>, Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static
Date: Fri, 3 Dec 2021 14:25:05 +0300 [thread overview]
Message-ID: <20211203112505.GI9522@kadam> (raw)
In-Reply-To: <888F3743-AB98-41A6-9651-EFDE5987AA01@oracle.com>
On Tue, Nov 30, 2021 at 08:19:47PM +0000, Chuck Lever III wrote:
> >
> > -DEFINE_SPINLOCK(nfsd_notifier_lock);
> > +static DEFINE_SPINLOCK(nfsd_notifier_lock);
> > static int nfsd_inetaddr_event(struct notifier_block *this, unsigned long event,
> > void *ptr)
> > {
> >
>
> Thanks! This was pushed to the tip of the for-next branch at
>
> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
>
> I removed the Fixes: line because a backport is unnecessary, and
> the commit ID is not yet permanent.
Removing the tag, makes it more complicated for backporters. Before
they could tell automatically from the Fixes tag that backporting was
not necessary.
On the other hand, does this patch really need a Fixes tag since it's
not a runtime bug? Different maintainers take different sides in that
argument.
If the patch needed a fixes tag then a lot of maintainers have scripts
to update the tag during a rebase. There are also automated tool run on
linux-next which emails a warning when the Fixes tags point to an
invalid hash.
regards,
dan carpenter
next prev parent reply other threads:[~2021-12-03 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 11:34 [PATCH -next] NFSD: make symbol 'nfsd_notifier_lock' static Wei Yongjun
2021-11-30 20:19 ` Chuck Lever III
2021-12-03 11:25 ` Dan Carpenter [this message]
2021-12-03 15:17 ` Chuck Lever III
2021-12-03 15:19 ` Bruce Fields
2021-12-03 15:28 ` Chuck Lever III
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=20211203112505.GI9522@kadam \
--to=dan.carpenter@oracle.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=hulkci@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=weiyongjun1@huawei.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 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.