From: yangerkun <yangerkun@huawei.com>
To: Chuck Lever III <chuck.lever@oracle.com>,
Christoph Hellwig <hch@infradead.org>
Cc: "zlang@kernel.org" <zlang@kernel.org>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"yoyang@redhat.com" <yoyang@redhat.com>
Subject: Re: [PATCH v2 2/2] generic/732: don't run it on tmpfs
Date: Mon, 29 Jul 2024 22:30:01 +0800 [thread overview]
Message-ID: <b24149f5-584a-86fb-0922-2413391f58d8@huawei.com> (raw)
In-Reply-To: <4E63C821-3231-4939-980C-D2F904138518@oracle.com>
在 2024/7/29 22:24, Chuck Lever III 写道:
>
>
>> On Jul 29, 2024, at 10:21 AM, Chuck Lever III <chuck.lever@oracle.com> wrote:
>>
>>
>>
>>> On Jul 29, 2024, at 10:16 AM, Christoph Hellwig <hch@infradead.org> wrote:
>>>
>>> Looks good:
>>>
>>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>>>
>>
>> I would prefer this test continue to run on tmpfs.
>>
>> tmpfs is broken, and needs to be fixed. If the generic/732
>> failure is an issue, then add it to the expunge list --
>> it found a real bug, that, once fixed, we don't want to
>> reappear.
>
> Never mind.
>
> Christoph, you deleted the context for this, and the
> Subject: was one character different than the one for
> generic/736. Even properly dosed on caffeine I missed
> that.
Aha, got it.
>
> --
> Chuck Lever
>
>
next prev parent reply other threads:[~2024-07-29 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 8:47 [PATCH v2 1/2] generic/732: remove unused code Yang Erkun
2024-07-29 8:47 ` [PATCH v2 2/2] generic/732: don't run it on tmpfs Yang Erkun
2024-07-29 14:16 ` Christoph Hellwig
2024-07-29 14:21 ` Chuck Lever III
2024-07-29 14:24 ` Chuck Lever III
2024-07-29 14:30 ` yangerkun [this message]
2024-07-29 14:28 ` yangerkun
2024-07-29 14:16 ` [PATCH v2 1/2] generic/732: remove unused code Christoph Hellwig
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=b24149f5-584a-86fb-0922-2413391f58d8@huawei.com \
--to=yangerkun@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=chuck.lever@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=yoyang@redhat.com \
--cc=zlang@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