2026-01-15 12:52 AM
I opened a PR on https://github.com/STMicroelectronics/u-boot.git for a patch that is applicable only downstream, and since I did not receive any response, I contacted Patrice Chotard, who told me to contact you for submitting downstream patches.
In addition to U-Boot, I have patches to submit to:
Could you please guide me on how I should proceed?
Thanks and regards,
Dario
2026-02-02 6:20 AM
Hello Dario,
you have to submit a PR for every other components like you did on U-boot. If there are some dependencies between the PRs please indicate it as a reference (for ex, if u-boot is the major PR, please mention it in the others PR).
2026-02-02 6:35 AM
u-boot PR is https://github.com/STMicroelectronics/u-boot/pull/5 I guess ...
2026-02-03 11:14 PM
Yes, exactly, that is the pull request, and precisely because I didn't see any review feedback, I wrote to Patrice Chotard who, in turn, directed me to the support team. This was his response:
"Hi Dario, In order to submit downstream changes, submit your changes directly to support teams using the forum: https://community.st.com/t5/stm32-mpus/ct-p/stm32-mpus. Nevertheless, i directly entered an internal ticket. I will have a look at it. As we are currently preparing a new release, this issue will be part of the next one expected latter this year. Thanks, Patrice"
So, has anything changed regarding this? That is, can I expect all downstream patches as well as meta-st layers to accept patches from GitHub?
Thanks and regards,
Dario Binacchi
2026-02-03 11:43 PM
Hello Dario, your PR will be integrated with other corrections on the release v6.2.1 planned in June.
v6.2.0 is under final tests and delivery. It will be delivered in W08 (too late for this PR).
2026-02-06 12:50 AM
And to answer your question: Yes, you have to submit a PR in each below component.
"In addition to U-Boot, I have patches to submit to:
https://github.com/STMicroelectronics/linux.git
https://github.com/STMicroelectronics/meta-st-openstlinux.git