From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Swarna Prabhu <sw.prabhu6@gmail.com>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"xiang@kernel.org" <xiang@kernel.org>,
"david@redhat.com" <david@redhat.com>,
"huang.ying.caritas@gmail.com" <huang.ying.caritas@gmail.com>,
"willy@infradead.org" <willy@infradead.org>,
"jack@suse.cz" <jack@suse.cz>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"p.raghav@samsung.com" <p.raghav@samsung.com>,
"da.gomez@samsung.com" <da.gomez@samsung.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"gost.dev@samsung.com" <gost.dev@samsung.com>,
Swarna Prabhu <s.prabhu@samsung.com>
Subject: Re: [PATCH] generic/750 : add missing _fixed_by_git_commit line to the test
Date: Wed, 2 Apr 2025 05:51:31 +0000 [thread overview]
Message-ID: <04df9945-d135-41a3-b8f0-77abad958188@wdc.com> (raw)
In-Reply-To: <20250401022921.983259-1-s.prabhu@samsung.com>
On 01.04.25 04:30, Swarna Prabhu wrote:
> -# We still deadlock with this test on v6.10-rc2, we need more work.
> -# but the below makes things better.
> _fixed_by_git_commit kernel d99e3140a4d3 \
> "mm: turn folio_test_hugetlb into a PageType"
>
> +#merged on v6.11-rc4
> +_fixed_by_git_commit kernel 2e6506e1c4ee \
> + "mm/migrate: fix deadlock in migrate_pages_batch() on large folios"
> +
Do we really need the version information? It's kind of redundant when
you have a commit hash.
next prev parent reply other threads:[~2025-04-02 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 2:29 Swarna Prabhu
2025-04-01 13:40 ` Luis Chamberlain
2025-04-02 5:51 ` Johannes Thumshirn [this message]
2025-04-02 18:29 ` Swarna
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=04df9945-d135-41a3-b8f0-77abad958188@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=da.gomez@samsung.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=huang.ying.caritas@gmail.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=patches@lists.linux.dev \
--cc=s.prabhu@samsung.com \
--cc=sw.prabhu6@gmail.com \
--cc=willy@infradead.org \
--cc=xiang@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