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.
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.
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.
Ian
