Searched refs:relevant (Results 1 – 25 of 777) sorted by relevance
12345678910>>...32
112 unsigned int relevant; in r300_swizzle_is_native() local133 relevant = 0; in r300_swizzle_is_native()137 relevant |= 1 << j; in r300_swizzle_is_native()139 if ((reg.Negate & relevant) && ((reg.Negate & relevant) != relevant)) in r300_swizzle_is_native()
186 unsigned int relevant; in r500_swizzle_is_native() local224 relevant = 0; in r500_swizzle_is_native()228 relevant |= 1 << i; in r500_swizzle_is_native()230 if ((reg.Negate & relevant) && ((reg.Negate & relevant) != relevant)) in r500_swizzle_is_native()
82 version, the relevant commits should already include the `NAPI_EXPERIMENTAL`114 If this release includes runtime behavior version guards, the relevant commits126 If this release includes add-on tests for the new Node-APIs, the relevant145 version and are necessary to document, the relevant commits should already167 released in this version and are necessary to document, the relevant commits201 good place to @-mention the relevant contributors.
42 Sync methods are only relevant for `rimraf.sync()`, of course.58 Only relevant for async usage.69 Only relevant for async usage.
34 important/relevant items from the changelog (see [`c61870c`][] for an62 important/relevant items from the changelog.82 important/relevant items from the changelog.
6 particularly relevant to testing Mesa because we often need to change41 ``/etc/lava-dispatcher/device-types``). Now, go find a relevant79 relevant as we have many stable branches all using CI).
5 independently covers all of the relevant information currently included here.
8 echo Building relevant projects.
2 # only where it's not relevant to the parse.
12 # Not relevant to Android.
51 [Playground link with relevant code](https://www.typescriptlang.org/play?#code/PTAEFkE9QYwewCYFNQHM…55 <!-- Please post the relevant code sample here as well-->
40 relevant commit:55 relevant commit:
8 Include details such as links relevant specs or previous discussions.
45 if necessary. Try and trim the log to relevant parts.69 Copy relevant output from the standard output and/or error channels.
12 highly relevant to text processing. In addition, see the documentation for
10 relevant sections.
8 4 YES * EINVAL and EAGAIN are relevant to low-priority mutex
25 # the relevant user config file. Reverting any general or extension34 # relevant settings from the default file.
8 relying on these headers are excluded. This is relevant for environments where these I/O functions …
5 // This is particularly relevant because our inliner replaces return statements with continue.
16 It gets manually pushed anytime there's an update to the Dockerfile or relevant46 It gets manually pushed anytime there's an update to the Dockerfile or relevant
13 relevant.
2 // type parameter names are relevant when choosing whether to merge interface declarations