Skip to content
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

[nrf noup] sample/smp_svr: nrf54l15dk test cases #2237

Conversation

michalek-no
Copy link
Contributor

fixup! [nrf noup] samples/smp_svr: nrf54l15pdk ext-flash partition

Added nrf54l15dk testcases as copies of nrf54l15pdk.

backport of #2167

moved from #2168

fixup! [nrf noup] samples/smp_svr: nrf54l15pdk ext-flash partition

Added nrf54l15dk testcases as copies of nrf54l15pdk.

Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
@rlubos
Copy link
Contributor

rlubos commented Nov 6, 2024

@michalek-no No need to backport sdk-zephyr PRs manually, just add the backport label in the original PR, it will be backported automatically when merged.

@michalek-no
Copy link
Contributor Author

@michalek-no No need to backport sdk-zephyr PRs manually, just add the backport label in the original PR, it will be backported automatically when merged.

no way to update #2168 due to single origin branch. And there is a mess as you can see.

@rlubos
Copy link
Contributor

rlubos commented Nov 6, 2024

@michalek-no No need to backport sdk-zephyr PRs manually, just add the backport label in the original PR, it will be backported automatically when merged.

no way to update #2168 due to single origin branch. And there is a mess as you can see.

I'm not asking to modify #2168, I'm asking to add backport label to #2167 instead of creating PRs manually at all. It's the cleanest and most manageable way to handle those sdk-zephyr PRs towards release branch.

@michalek-no michalek-no closed this Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants