From: Radu Rendec on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3921#note_2547504081
> It is currently a no-op in RHEL since `ARCH_RENESAS is not set`. Having it set is misleading, and I'm not sure why the config checker didn't catch it. Maybe the config checker catches only conflicting configs, not redundant ones. > We don't? It's disabled by `ARCH_RENESAS is not set` in rhel and `CONFIG_ARCH_R9A09G056 is not set` in rhel/automotive. I thought in the absence of an explicit config file it would default to `y` (for rhel) but completely overlooked the fact that `ARCH_RENESAS` was disabled in rhel. Sorry for the confusion! > I think I pushed the commits right after your review, hence the misunderstanding. No, you must had pushed them before because I could see them, with the sha1 hashes you mentioned. > `CONFIG_ARCH_R9A09G047` should not be set in rhel/automotive, hence moving the configuration down to automotive. I can send a separate MR if you prefer, but I thought it might as well go with this one. No, I don't feel strongly about it. I was just confused because it was outside of the scope of the initial version of the MR (created by automation). -- _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
