From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Colin King <colin.king@canonical.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] nfsd: fix check of statid returned from call to find_stateid_by_type
Date: Thu, 28 Jan 2021 13:50:42 -0500 [thread overview]
Message-ID: <20210128185042.GB29887@fieldses.org> (raw)
In-Reply-To: <80ACEDFA-B496-44E0-AABB-BD4A7826516B@oracle.com>
On Thu, Jan 28, 2021 at 03:53:36PM +0000, Chuck Lever wrote:
> > On Jan 28, 2021, at 10:34 AM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> > Fixes tags are used for a lot of different things:
> > 1) If there is a fixes tag, then you can tell it does *NOT* have to
> > be back ported because the original commit is not in the stable
> > tree. It saves time for the stable maintainers.
> > 2) Metrics to figure out how quickly we are fixing bugs.
> > 3) Sometimes the Fixes tag helps because we want to review the original
> > patch to see what the intent was.
> >
> > All sorts of stuff. Etc.
>
> Yep, I'm a fan of all that. I just want to avoid poking the stable
> automation bear when it's unnecessary.
I've routinely had patches with Fixes: lines referencing other queued-up
patches, and I didn't get any stable mail about it.
100% not something to worry about.
--b.
prev parent reply other threads:[~2021-01-28 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 14:49 Colin King
2021-01-28 15:05 ` Chuck Lever
2021-01-28 15:17 ` Bruce Fields
2021-01-28 15:34 ` Dan Carpenter
2021-01-28 15:53 ` Chuck Lever
2021-01-28 18:50 ` Bruce Fields [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=20210128185042.GB29887@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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
all inboxes | Powered by JetHome®