From: Pavel Machek <pavel@ucw.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Hugh Dickins <hughd@google.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Yang Shi <shy828301@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH AUTOSEL 13/14] mm/thp: ClearPageDoubleMap in first page_add_file_rmap()
Date: Mon, 2 May 2022 10:45:54 +0200 [thread overview]
Message-ID: <20220502084554.GA358@ucw.cz> (raw)
In-Reply-To: <YmrHsVZTEzqIDiKd@kroah.com>
Hi!
> > I've chosen to answer to this patch of my 3 in your 14 AUTOSELs,
> > because this one is just an improvement, not at all a bugfix needed
> > for stable (maybe AUTOSEL noticed "racy" or "safely" in the comments,
> > and misunderstood). The "Fixes" was intended to help any humans who
> > wanted to backport into their trees.
>
> This all was off of the Fixes: tag. Again, if these commits fix
> something why are they not for stable? I'm a human asking to backport
> these into the stable trees based on that :)
I see this as a repeated pattern: People add Fixes: tag for trivial
things that should not really go to stable (typo in comment?) and
stable takes it is a serious bug that needs to be fixed in stable.
Best regards,
Pavel
prev parent reply other threads:[~2022-05-02 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220428154222.1230793-1-gregkh@linuxfoundation.org>
[not found] ` <20220428154222.1230793-13-gregkh@linuxfoundation.org>
2022-04-28 16:51 ` Hugh Dickins
2022-04-28 16:58 ` Greg Kroah-Hartman
2022-04-28 19:27 ` Hugh Dickins
2022-04-28 22:45 ` Sean Christopherson
2022-04-29 12:13 ` Greg Kroah-Hartman
2022-04-30 0:27 ` Sasha Levin
2022-05-02 8:45 ` Pavel Machek [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=20220502084554.GA358@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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