[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <187C3E49-A977-492E-99CB-97F032B24E5F@oracle.com>
Date: Thu, 22 Jun 2023 17:12:37 +0000
From: Chuck Lever III <chuck.lever@...cle.com>
To: stsp <stsp2@...dex.ru>
CC: Jeff Layton <jlayton@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Shuah Khan <shuah@...nel.org>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>
Subject: Re: [PATCH 2/2] selftests: add OFD lock tests
> On Jun 22, 2023, at 1:05 PM, stsp <stsp2@...dex.ru> wrote:
>
>
> 22.06.2023 21:58, Chuck Lever III пишет:
>> IMO that's not a reason not to do this properly.
>>
>> You should work with Jeff and the maintainer of
>> xfstests to make it happen.
> But its not going to be in this patch-set
> anyway, as its a different source tree...
If others agree with me, then please drop the selftests
patch from this series. There is a considerably higher
probability that the new test will be run frequently
by CI if it's in xfstests.
> So I should prepare it when this is merged,
> or?
I don't have a strong preference. A good choice is to
push the test before the kernel changes are merged.
--
Chuck Lever
Powered by blists - more mailing lists