Lines Matching refs:changes

65 When the API changes status to unstable API, mark the API version in the headers
91 minor changes. Backwards-compatibility will be maintained if reasonable.
104 #. A Pull Request must be opened that changes the corresponding entry in the
113 When the API changes status to stable API, mark the API version in the headers
119 Introducing breaking API changes
147                    - Function call changes
148                    - Device Tree changes (source and bindings)
149                    - Kconfig option changes
154    Instead of a written description of the changes, the RFC issue may link to a
155    Pull Request containing those changes in code form.
175 - The actual changes to the API
182 - The changes required to adapt in-tree users of the API to the change.
200 The API version shall be changed to signal backward incompatible changes. This
202 include minor and patch level changes. Patch and minor versions MUST be reset to
207    Breaking API changes will be listed and described in the migration guide.