I'm working on upstreaming vendor patches for the Orange Pi RV2 board, currently available at: https://github.com/OctopusET/u-boot-orangepi/pull/1/commits
I'm rebasing these patches onto the latest U-Boot branch (v2025.04-rc5). To ensure the patches meet upstream standards, I have a few questions: 1. What specific steps should I take after rebasing to prepare these patches for upstream submission? 2. The current patch set is quite large. Should I split it into smaller, more focused patches? If so, what would be the recommended approach for splitting? 3. Are there any particular coding style or documentation requirements I should be aware of for the Orange Pi RV2 board support? 4. How should I handle any vendor-specific code that may not be suitable for upstream? 5. Are there any maintainers or subsystem-specific mailing lists I should include when submitting these patches? Any guidance or best practices for upstreaming vendor patches would be greatly appreciated. Thank you for your time and assistance.
