Searched full:around (Results 1 – 25 of 3673) sorted by relevance
12345678910>>...147
17 * This work-around is implemented in PBI, so just check to see if the18 * work-around was actually applied. To do this, we check for specific data43 printf("Work-around for Erratum A004849 is not enabled\n"); in check_erratum_a4849()64 printf("Work-around for Erratum A004849 is not enabled\n"); in check_erratum_a4849()68 /* Everything matches, so the erratum work-around was applied */ in check_erratum_a4849()70 printf("Work-around for Erratum A004849 enabled\n"); in check_erratum_a4849()76 * This work-around is implemented in PBI, so just check to see if the77 * work-around was actually applied. To do this, we check for specific data80 * The work-around says that for each SerDes lane, write BnTTLCRy0 =104 printf("Work-around for Erratum A004580 is " in check_erratum_a4580()[all …]
63 * 2AP. worked around in hardware66 * 4AP. worked around in hardware88 * 3AP. We work around this92 * 6AP. not affected - worked around in hardware93 * 7AP. not affected - worked around in hardware94 * 8AP. worked around in hardware - we get explicit CS errors if not98 * 10AP. not affected - worked around in hardware102 * 12AP. not affected - worked around in hardware103 * 13AP. not affected - worked around in hardware105 * 15AP. not affected - worked around in hardware[all …]
24 file://0005-crashdump-elf.c-work-around-for-sysconf-_SC_NPROCESS.patch \25 file://0006-kexec-syscall.h-work-around-missing-syscall-wrapper.patch \26 file://0007-kexec.c-add-guard-around-ENOTSUP.patch \28 file://0009-vmcore-dmesg.c-work-around-missing-imaxdiv.patch \29 file://0010-fs2dt.c-work-around-missing-getline.patch \
7 This uclass allows you to play around with driver model. It provides16 This device allows you to play around with driver model. It prints25 This device allows you to play around with driver model. It prints
20 * around quickly. Locking rules (if necessary) have to be defined40 * cycle counter wrap around. Initialize with45 * more often than the cycle counter wraps around. The nanosecond46 * counter will only wrap around after ~585 years.
34 * To work around it we hide the relationship of the pointer and the object38 * RELOC_HIDE could trash r30. The bug can be worked around by changing66 * Adding an empty inline assembly before it works around the problem95 * Work it around via a compiler barrier quirk suggested by Jakub Jelinek.
99 * This function is intended to simplify locking around refcounting for102 * Operations on such objects require at least a read lock around103 * lookup + kref_get, and a write lock around kref_put + remove from lookup
5 work around CVE-2021-45444 in VCS_Info29 + can optionally be used to work around recursive PROMPT_SUBST44 +Subject: [PATCH] security/89: Partially work around CVE-2021-45444 in VCS_Info49 +This patch is a partial, VCS_Info-specific work-around for CVE-2021-45444,54 +The patch works around the vulnerability by pre-escaping values substituted
13 * Work around certain R4000 CPU errata (as implemented by GCC):39 * Work around certain R4400 CPU errata (as implemented by GCC):53 * Work around the "daddi" and "daddiu" CPU errata:
51 \details Around a linestring, a buffer can be defined left or right.52 Around a polygon, assumed clockwise internally,59 \brief Enumerates types of pieces (parts of buffer) around geometries
313 bool "Enable linker work around for PPC476FPE errata #46"315 This option enables a work around for an icache bug on 476320 The work around enables the appropriate linker options and322 page boundaries. The work around is only required when
15 landlock: Use square brackets around "landlock-ruleset"21 carry square brackets around their name:35 1cdc415f1083 ("uapi, fsopen: use square brackets around "fscontext" [ver #2]")
7 To work around <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91691>14 patch adds the same disabling around the definition of that variable,21 (clntudp_call): Disable -Wmaybe-uninitialized around declaration
33 \brief Create a circular buffer around a point36 It creates a circular buffer around a point. It can be applied62 //! Fills output_range with a circle around point using distance_strategy
31 It creates a sharp corners around each convex vertex. It can be applied57 //! \param miter_limit The miter limit, to avoid excessively long miters around sharp corners63 //! Fills output_range with a sharp shape around a vertex
244 Again, these primitives provide explicit memory barrier semantics around251 provide explicit memory barrier semantics around the operation::257 This primitive must provide explicit memory barrier semantics around268 atomic_xchg must provide explicit memory barriers around the operation. ::277 atomic_cmpxchg must provide explicit memory barriers around the operation,292 atomic_add_unless must provide explicit memory barriers around the298 If a caller requires memory barrier semantics around an atomic_t486 must provide explicit memory barrier semantics around their execution.510 If explicit memory barriers are required around {set,clear}_bit() (which do
196 /* Read didn't wrap around the buffer */ in saa7164_bus_set()254 /* Additional data wraps around the ring */ in saa7164_bus_set()350 /* Write doesn't wrap around the ring */ in saa7164_bus_get()353 /* Write wraps around the ring */ in saa7164_bus_get()409 /* Write doesn't wrap around the ring */ in saa7164_bus_get()412 /* Write wraps around the ring */ in saa7164_bus_get()439 /* Additional data wraps around the ring */ in saa7164_bus_get()
68 some problem that could not be worked around.108 prescribed bus turn-around time113 prescribed bus turn-around time124 prescribed bus turn-around time. This error170 be worked around, such as a physical
... Dickey 65+- modify clean-rule to work around Fedora NFS bugs. 66+ 67 * Sat Sep ...
20 development around the MPC86X processor families.30 development around the MPC885 processor family.119 to disable it if you have worked around the bug in the compiler
16 /* flip source image horizontally (around the vertical axis) */ …18 /* flip source image vertically (around the horizontal axis)*/ …
18 time around 2009: http://slirp.sourceforge.net/22 around May 2009 which archived it in 2012
156 /* probe for new spot, wrapping around */ in resizeHash()178 * We probe on collisions, wrapping around the table.204 if (pEntry == pEnd) { /* wrap around to start */ in mzHashTableLookup()274 if (pEntry == pEnd) { /* wrap around to start */ in mzHashTableRemove()337 if (pEntry == pEnd) { /* wrap around to start */ in countProbes()
37 still be around and under development a decade from now.76 around.85 around. So it is always a good idea to remind reviewers of previously181 it with the assumption that you will not be around to maintain it201 eventually flow around you and get into the mainline anyway. In the Linux
155 /* probe for new spot, wrapping around */ in resizeHash()177 * We probe on collisions, wrapping around the table.204 if (pEntry == pEnd) { /* wrap around to start */ in mzHashTableLookup()275 if (pEntry == pEnd) { /* wrap around to start */ in mzHashTableRemove()339 if (pEntry == pEnd) { /* wrap around to start */ in countProbes()