-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it acceptable to create a PR for mbed-os-5.15.x versions #13616
Comments
@mbedNoobNinja thank you for raising this issue.Please take a look at the following comments: We cannot automatically identify a release based on the version of Mbed OS that you have provided. NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered. |
Target update
The question is how should I proceed 1 PR per component feature or device_has |
Yes, ti should not be a problem. I'll close this question. |
Description of defect
I thought that #13125 is the last version but suddenly an #13381 appeared!
If PR are still accepted, how should I structure them if I want to add support for:
components: ["
SD
", "FLASHIAP
"]device_has: ["
USBDEVICE
", "FLASH
", "LPTICKER
"]bootloader_supported [:
true
]SD will be with external lib, (probably with the name SDHI), because it does not use SPI bus, but the native SDHI controller, similar to some of the Nuvoton boards!
Target(s) affected by this defect ?
VK_RZ_A1H
Toolchain(s) (name and version) displaying this defect ?
ARM
,GCC_ARM
,IAR
What version of Mbed-os are you using (tag or sha) ?
#13125
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
Tool
Version
How is this defect reproduced ?
None
The text was updated successfully, but these errors were encountered: