[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210128185042.GB29887@fieldses.org>
Date: Thu, 28 Jan 2021 13:50:42 -0500
From: Bruce Fields <bfields@...ldses.org>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
Colin King <colin.king@...onical.com>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][next] nfsd: fix check of statid returned from call to
find_stateid_by_type
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@...cle.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.
Powered by blists - more mailing lists