Lines Matching refs:change

175 change (which may bring big improvements) which causes something to break
176 for existing users.  This kind of change is called a "regression," and
184 change if it brings new functionality to ten systems for each one it
195 An especially unwelcome type of regression is any sort of change to the
374 needs, that may be a sign that the API needs to change.  As a kernel
378 to be well justified.  So any patch making an internal API change should be
379 accompanied by a description of what the change is and why it is
380 necessary.  This kind of change should also be broken out into a separate
385 which is broken by the change.  For a widely-used function, this duty can
392 When making an incompatible API change, one should, whenever possible,
396 a change that they need to respond to.  Supporting out-of-tree code is not