From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: David Howells <dhowells@redhat.com>,
Ira Weiny <ira.weiny@intel.com>,
Eric Sandeen <sandeen@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel@vger.kernel.org,
linux-man <linux-man@vger.kernel.org>,
linux-kernel@vger.kernel.org, xfs <linux-xfs@vger.kernel.org>,
linux-ext4@vger.kernel.org, Xiaoli Feng <xifeng@redhat.com>
Subject: Re: [PATCH V2] uapi: fix statx attribute value overlap for DAX & MOUNT_ROOT
Date: Wed, 2 Dec 2020 20:06:01 +0100 [thread overview]
Message-ID: <X8flmVAwl0158872@kroah.com> (raw)
In-Reply-To: <CAJfpegsQxi+_ttNshHu5MP+uLn3px9+nZRoTLTxh9-xwU8s1yg@mail.gmail.com>
On Wed, Dec 02, 2020 at 06:41:43PM +0100, Miklos Szeredi wrote:
> On Wed, Dec 2, 2020 at 5:24 PM David Howells <dhowells@redhat.com> wrote:
> >
> > Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > > Stable cc also?
> > >
> > > Cc: <stable@vger.kernel.org> # 5.8
> >
> > That seems to be unnecessary, provided there's a Fixes: tag.
>
> Is it?
>
> Fixes: means it fixes a patch, Cc: stable means it needs to be
> included in stable kernels. The two are not necessarily the same.
>
> Greg?
You are correct. cc: stable, as is documented in
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
ensures that the patch will get merged into the stable tree.
Fixes: is independent of it. It's great to have for stable patches so
that I know how far back to backport patches.
We do scan all commits for Fixes: tags that do not have cc: stable, and
try to pick them up when we can and have the time to do so. But it's
not guaranteed at all that this will happen.
I don't know why people keep getting confused about this, we don't
document the "Fixes: means it goes to stable" anywhere...
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-02 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 23:21 [PATCH V2] uapi: fix statx attribute value overlap for DAX & MOUNT_ROOT Eric Sandeen
2020-12-02 4:18 ` Darrick J. Wong
2020-12-02 8:06 ` Christoph Hellwig
2020-12-02 16:00 ` Ira Weiny
2020-12-02 16:18 ` Miklos Szeredi
2020-12-02 16:23 ` David Howells
2020-12-02 17:41 ` Miklos Szeredi
2020-12-02 19:06 ` Greg Kroah-Hartman [this message]
2020-12-02 20:40 ` Dave Chinner
2020-12-02 21:04 ` Greg Kroah-Hartman
2020-12-03 1:50 ` Dave Chinner
2020-12-03 6:18 ` Amir Goldstein
2020-12-04 16:02 ` Theodore Y. Ts'o
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=X8flmVAwl0158872@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dhowells@redhat.com \
--cc=ira.weiny@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=sandeen@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=xifeng@redhat.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;
as well as URLs for NNTP newsgroup(s).