Re: [OS-BUILD PATCHv3 0/5] ark: Set Architecture Level Set to Z14 for s390

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Philipp Rudo on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_595402767

Hi,

sorry for the late response.

here's the v3 with what I picked up from the discussion, in particular
improve the wording of the first two commit messages and leave the
rest as is.

While preparing v3 I noticed a nit in the first commit. In v3 I have
disabled (=n) the config instead of using its default (=y) as the
config requires LLD to work. I'm wondering why the pipelines didn't
find this the way I see it this should have caused a build bug.

I took this as a reason to have a closer look on the resulting configs
and found that there are more changes than I had expected. For example
on ppc CONFIG_LIVEPATCH now gets enabled, where I'm not sure if it is
intended or not. At least in RHEL8 there is no livepatch support for
ppc.
An other example (also ppc) is CONFIG_DYNAMIC_FTRACE_WITH_REGS which
also gets enabled now. What surprised me in this case is that I
couldn't find a way to disable that option. Every test I made resulted
in process_configs.sh to abort complaining about a configs mismatch.
What confuses me is that I couldn't find any other config that selects
this one. So I have no clue what overwrites my manually set value.

Long story short, I'm afraid that switching to the dummy-tools is less
straight forward than I thought in the first place. Thus I'm wondering
if it wouldn't be better to move the change to it's own MR together
with a thorough review of the resulting configs. My problem with this
is that I'll be leaving my current job end of next week and thus have
tons of other stuff on my mind at the moment. Meaning that someone else
would need to take over that task

Any comments/opinions?

Thanks and sorry for the long comment
Philipp
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux