Lines Matching full:change

53 First, let's try making a change to a UAPI header file that obviously
81 Let's add another change that *might* break userspace::
106           1 data member change:
116 In this case, the script is reporting the type change because it could
129 Now, let's make a similar change that *will* break userspace::
163 Let's commit the breaking change, then commit the innocuous change::
165     % git commit -m 'Breaking UAPI change' include/uapi/linux/bpf.h
166     [detached HEAD f758e574663a] Breaking UAPI change
168     % git commit -m 'Innocuous UAPI change' include/uapi/linux/acct.h
169     [detached HEAD 2e87df769081] Innocuous UAPI change
180 It doesn't catch any breaking change because, by default, it only
181 compares ``HEAD`` to ``HEAD^1``. The breaking change was committed on
207 Consider this change::
222 This is a change to an arm64-specific UAPI header file. In this example, I'm
257 change is reported properly. Also notice that the total number of UAPI
264 Consider this change::
282 this change::
298     include/linux/eventpoll.h did not change between HEAD and dirty tree...
299     It's possible a change to one of the headers it includes caused this error:
303 Note that the script noticed the failing header file did not change,
310 Consider this change::
338 Removing a UAPI header is considered a breaking change, and the script
388 Depending on how a structure is handled in kernelspace, a change which
402 By default, the script will flag this kind of change for further review::
410 However, it is possible that this change was made safely.
450 This change would be flagged by the script::
454       1 data member change:
467 it's possible there are some cases where the script flags a change
468 which does not break UAPI. It's also possible a change which *does*