From: Rupinderjit Singh on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3857#note_2534138630 Hi Brian. Please find the comments below: * The merge request needs to be rebased against the latest kernel-ark. [Rupinder]: I'm still working on adding few more configs. Apologies, I should've moved it to draft state to reflect the WIP. I'll do that now and re- open it for review once ready with all the changes, and rebased. * Which QC platforms are intended to be enabled by this merge request? RB3 Gen2? Any others? I see `CONFIG_INTERCONNECT_QCOM_MSM8916=m`, and my understanding is that's a 10+ year-old SoC at this point. [Rupinder]: Mostly, this is around Rb3Gen2+QCS6490. But, we have potential few more devices (different boards) for the enablement based on QCS6490. Yes, 8196 is old and I think I ended up enabling it due to some dependency becuase I'm using fedora configs as reference for adding Qualcomm configs in RHEL. I'll check on this and omit those not nedded. * There needs to be some discussion within RH about which teams will support some of these components. [Rupinder]: Agree with that. I started some discussion around managining the configs for edge devices. We haven't reached to any conclusion yet and as we have customer device ready and shipped to us based on RB3Gen2, so I started adding the configs to avoid any dealys. Discussion are paused for now, but I'll resume it once this is done. Btw, are you referring to Qualcomm specific configs, or in general? Please loop me and Greg Nicholas into these discussions. * Would it be possible to split this up into several smaller MRs that are easier to review? For example, the V4L changes could go in it's own MR. Whatever team within RHEL that will support this can review it. [Rupinder]: I'm already working on splitting it into multiple commits. I'll create multiple MRs smaller MRs as you suggested. -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
