From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Chun Ng <chunn@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Ankita Garg <ankitag@nvidia.com>
Subject: Re: [REGRESSION]: mmap performance regression starting with k-6.1
Date: Fri, 24 Nov 2023 07:15:34 +0700 [thread overview]
Message-ID: <ZV_rJtxdn1dU9ip0@archie.me> (raw)
In-Reply-To: <ZV9x6qZ5z8YTvTC4@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
On Thu, Nov 23, 2023 at 03:38:18PM +0000, Matthew Wilcox wrote:
> On Thu, Nov 23, 2023 at 12:07:40PM +0700, Bagas Sanjaya wrote:
> > Anyway, I'm adding this regression to regzbot:
> >
> > #regzbot ^introduced: v6.0..v6.1
>
> this is not a regression. close it, you idiot.
>
>
why?
Confused...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-24 0:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 20:03 [REGRESSION]: mmap performance regression starting with k-6.1 Chun Ng
2023-11-23 1:18 ` Bagas Sanjaya
2023-11-23 3:06 ` Chun Ng
2023-11-23 5:01 ` Bagas Sanjaya
2023-11-23 5:07 ` Bagas Sanjaya
2023-11-23 14:34 ` Liam R. Howlett
2023-11-24 5:08 ` Linux regression tracking #update (Thorsten Leemhuis)
[not found] ` <20231126071854.19490-1-00107082@163.com>
2023-11-26 13:47 ` Matthew Wilcox
2023-11-23 15:38 ` Matthew Wilcox
2023-11-24 0:15 ` Bagas Sanjaya [this message]
2023-11-24 1:04 ` Matthew Wilcox
2023-11-24 11:52 ` Greg KH
2023-11-24 15:06 ` Matthew Wilcox
2023-11-24 15:13 ` Greg KH
2023-11-24 15:29 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-25 1:50 ` Chun Ng
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=ZV_rJtxdn1dU9ip0@archie.me \
--to=bagasdotme@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ankitag@nvidia.com \
--cc=chunn@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=regressions@lists.linux.dev \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).