Skip to content

[msft-202405][yang-model] support reserving mem in high region for crashkernel#1851

Merged
arlakshm merged 3 commits intoAzure:202405from
ysmanman:crashkernel-yang-model
Nov 27, 2025
Merged

[msft-202405][yang-model] support reserving mem in high region for crashkernel#1851
arlakshm merged 3 commits intoAzure:202405from
ysmanman:crashkernel-yang-model

Conversation

@ysmanman
Copy link
Contributor

@ysmanman ysmanman commented Nov 26, 2025

Why I did it

Cherry-pick sonic-net/sonic-buildimage#24441 in msft-202405.

Work item tracking
  • Microsoft ADO (number only):

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@ysmanman ysmanman requested a review from qiluo-msft as a code owner November 26, 2025 04:24
@ysmanman ysmanman changed the title support reserving mem in high region for crashkernel [msft-202405][yang-model] support reserving mem in high region for crashkernel Nov 26, 2025
@arlakshm arlakshm merged commit ea028e6 into Azure:202405 Nov 27, 2025
2 checks passed
ysmanman added a commit to ysmanman/sonic-buildimage-msft that referenced this pull request Nov 27, 2025
When cherry-pick sonic-net/sonic-buildimage#24441 in msft-202405,  Some typo and mistakes were made
in Azure#1851. Fix them accordingly.
@ysmanman ysmanman mentioned this pull request Nov 27, 2025
10 tasks
arlakshm pushed a commit that referenced this pull request Nov 28, 2025
When cherry-pick sonic-net/sonic-buildimage#24441 in msft-202405, Some
typo and mistakes were made in
#1851. Fix them
accordingly.

<!--
Please make sure you've read and understood our contributing guidelines:
     https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

** Make sure all your commits include a signature generated with `git
commit -s` **

If this is a bug fix, make sure your description includes "fixes #xxxx",
or
     "closes #xxxx" or "resolves #xxxx"

     Please provide the following information:
-->

#### Why I did it

##### Work item tracking
- Microsoft ADO **(number only)**:

#### How I did it

#### How to verify it

<!--
If PR needs to be backported, then the PR must be tested against the
base branch and the earliest backport release branch and provide tested
image version on these two branches. For example, if the PR is requested
for master, 202211 and 202012, then the requester needs to provide test
results on master and 202012.
-->

#### Which release branch to backport (provide reason below if selected)

<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->

- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
- [ ] 202106
- [ ] 202111
- [ ] 202205
- [ ] 202211

#### Tested branch (Please provide the tested image version)

<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->

- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->

#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->

<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under
sonic-utilities repo. where, Generic Config and Update feature has been
labelled as GCU.
-->

#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on
https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->

#### A picture of a cute animal (not mandatory but encouraged)
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.

2 participants