Lines Matching full:changes

24                    will use any dirty changes in tree to UAPI files. If there are no
25                    dirty changes, HEAD will be used.
31     -i             Ignore ambiguous changes that may or may not break UAPI compatibility.
78     Checking changes to UAPI headers between HEAD and dirty tree...
102     Checking changes to UAPI headers between HEAD and dirty tree...
120 anything. You can pass the ``-i`` flag to the script to ignore changes
126     Checking changes to UAPI headers between HEAD and dirty tree...
152     Checking changes to UAPI headers between HEAD and dirty tree...
156           2 data member changes:
177     Checking changes to UAPI headers between HEAD^1 and HEAD...
184 let's pass ``-p HEAD~2`` to the script so it checks UAPI changes between
190     Checking changes to UAPI headers between HEAD~2 and HEAD...
194           2 data member changes:
229     No changes to UAPI headers were applied between HEAD and dirty tree
240     Checking changes to UAPI headers between HEAD and dirty tree...
249           2 data member changes (1 filtered):
258 header files checked by the script changes. This is because the number
287     Checking changes to UAPI headers between HEAD and dirty tree...
291           2 data member changes:
333     Checking changes to UAPI headers between HEAD and dirty tree...
351     Checking changes to UAPI headers between v6.0 and v6.1...
357 so the script is unable to check changes before then.
359 You'll notice that the script detected many UAPI changes that are not
368 types of changes may be flagged even though they intentionally break UAPI.
378     Checking changes to UAPI headers between ba47652ba655^1 and ba47652ba655...
460 At this time, there's no way to filter these types of changes, so be
476 (and ideally a unit test in userspace) to make sure your UAPI changes