Lines Matching refs:script

7 The UAPI checker (``scripts/check-uapi.sh``) is a shell script which
73 Now, let's use the script to validate::
97 The script will catch this::
116 In this case, the script is reporting the type change because it could
120 anything. You can pass the ``-i`` flag to the script to ignore changes
147 and the script will report the breakage even if you pass ``-i``::
172 Now, let's run the script again with no arguments::
184 let's pass ``-p HEAD~2`` to the script so it checks UAPI changes between
202 base reference to ``HEAD~`` so then the script would compare it to ``HEAD~^1``.
223 running the script from an x86 machine with an x86 compiler, so, by default,
224 the script only checks x86-compatible UAPI header files::
232 script doesn't even try.
258 header files checked by the script changes. This is because the number
303 Note that the script noticed the failing header file did not change,
327 This script removes a UAPI header file from the install list. Let's run
328 the script::
338 Removing a UAPI header is considered a breaking change, and the script
356 Note: Before v5.3, a header file needed by the script is not present,
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
383 The script will always flag removals (even if they're intentional).
402 By default, the script will flag this kind of change for further review::
435 pass ``-i`` to the script, and struct expansions like this will be ignored.
440 While the script handles expansion into an existing flex array, it does
450 This change would be flagged by the script::
466 While many types of false positives are filtered out by the script,
467 it's possible there are some cases where the script flags a change
469 break userspace would not be flagged by this script. While the script
473 The intention is for this script to be used as a quick check for