From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Ian Kent <raven@themaw.net>,
linux-erofs@lists.ozlabs.org,
Jeffle Xu <jefflexu@linux.alibaba.com>
Subject: Re: Trying to work with the tests
Date: Wed, 24 Apr 2024 23:35:49 +0800 [thread overview]
Message-ID: <d1956835-a3b2-4e60-a0e7-3c0413bbcb7c@linux.alibaba.com> (raw)
In-Reply-To: <aca97115-f26f-4970-be4c-c84db4d11e15@themaw.net>
On 2024/4/24 18:37, Ian Kent wrote:
> On 24/4/24 17:47, Ian Kent wrote:
>> On 23/4/24 18:34, Gao Xiang wrote:
>>> Hi Ian,
>>>
>>> On 2024/4/22 21:10, Ian Kent wrote:
>>>> On 22/4/24 17:12, Gao Xiang wrote:
>>>>> Hi Ian,
>>>>>
>>>>> (+Cc Jingbo here).
>>>>>
>>>>> On 2024/4/22 16:31, Ian Kent wrote:
>>>>>> I'm new to the list so Hi to all,
>>>>>>
>>>>>>
>>>>>> I'm working with a heavily patched 5.14 kernel and I've gathered together patches to bring erofs
>>>>>>
>>>>>> up to 5.19 and I'm trying to run the erofs and fscache tests from a checkout of the 1.7.1 repo.
>>>>>>
>>>>>> (branch experimental-tests-fscache) and I have a couple of fails I can't quite work out so I'm
>>>>>>
>>>>>> hoping for a little halp.
>>>>>
>>>>> Thanks for your interest and provide the detailed infos.
>>>>>
>>>>> I guess a modified 5.14 kernel may be originated from RHEL 9?
>>>>
>>>> Yes, that's right.
>>>>
>>>> I am working on improving erofs support in RHEL which of course goes via CentOS Stream 9.
>>>
>>> BTW, could you submit the current patches to CentOS stream 9 mainline?
>>> so I could review as well.
>>
>> CentOS Stream is meant to allow our development to be public so, yes, I would like to do that.
>>
>>
>> It will be interesting to see how it works, I'll have a look around the CentOS web site to see if I can work
>>
>> out how it looks to external people.
>>
>>
>> Timing is good too as I'm about to construct a merge request and our process requires that to be against
>>
>> the CentOS Stream repo.
>>
>>
>> That repository is located on GitLab ... so we'll need to work out how to go about that.
>
> Looking at the CentOS web page at https://docs.centos.org/en-US/stream-contrib/quickstart/
>
> you would need a GitLab account to take part in the merge request review process.
Yes, I have a gitlab account.
>
>
> If you wanted to take part in the case discussion as well you would need a Red Hat Issues
>
> account (sign up https://issues.redhat.com/). This is only needed if you want to take part
>
> in development/log bug reports, etc. since a Jira bug is required for each merge request.
I guess I don't need a Red Hat Issues account, since I could comment in the PR itself.
>
>
> As the Mandalorian would say, "this is the way".
>
>
> If you don't wish to do this then I can post elsewhere, perhaps a kernel.org repo. but it gets
>
> a bit harder if we work outside of the development process.
Nope, gitlab repo is fine, and I already participated in CentOS
Stream 9 repo before.
Thanks,
Gao Xiang
>
>
> Ian
>
prev parent reply other threads:[~2024-04-24 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 8:31 Trying to work with the tests Ian Kent
2024-04-22 9:12 ` Gao Xiang
2024-04-22 11:30 ` Jingbo Xu
2024-04-22 13:20 ` Ian Kent
2024-04-22 13:10 ` Ian Kent
2024-04-23 10:34 ` Gao Xiang
2024-04-24 9:47 ` Ian Kent
2024-04-24 9:52 ` Gao Xiang
2024-04-24 10:37 ` Ian Kent
2024-04-24 15:35 ` Gao Xiang [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=d1956835-a3b2-4e60-a0e7-3c0413bbcb7c@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=raven@themaw.net \
/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).