| /openbmc/linux/scripts/coccinelle/free/ |
| H A D | ifnullfree.cocci | 5 /// "kfree(NULL) is safe this check is probably not required"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/konkretcmpi/ |
| H A D | konkretcmpi_0.9.2.bb | 3 KonkretCMPI makes CMPI provider development easier by generating type-safe \
|
| /openbmc/linux/arch/sparc/kernel/ |
| H A D | wof.S | 111 wr %glob_tmp, 0x0, %wim ! set new %wim, this is safe now
148 wr %glob_tmp, 0x0, %wim ! Now it is safe to set new %wim
|
| /openbmc/linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 124 <hardirq-safe> or <hardirq-unsafe>
125 <softirq-safe> or <softirq-unsafe>
127 This is because if a lock can be used in irq context (irq-safe) then it
159 <hardirq-safe> -> <hardirq-unsafe>
160 <softirq-safe> -> <softirq-unsafe>
162 The first rule comes from the fact that a hardirq-safe lock could be
164 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
175 - if a new hardirq-safe lock is discovered, we check whether it
178 - if a new softirq-safe lock is discovered, we check whether it took
182 hardirq-safe lock took it in the past.
[all …]
|
| /openbmc/linux/Documentation/w1/slaves/ |
| H A D | w1_ds2406.rst | 24 respectively. Bits 2-7 are ignored, so it's safe to write ASCII data.
|
| /openbmc/linux/Documentation/power/regulator/ |
| H A D | design.rst | 21 specific knowledge that these changes are safe to perform on this
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/indent/indent/ |
| H A D | 0001-Makefile.am-remove-regression-dir.patch | 12 BTW, it should be safe not to cover regression dir
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-pciback | 25 and the actual device is assigned to a HVM. It is not safe
|
| /openbmc/linux/Documentation/infiniband/ |
| H A D | core_locking.rst | 39 are therefore safe to call from any context.
46 the midlayer is also safe to call from any context.
|
| /openbmc/linux/arch/arm/boot/dts/qcom/ |
| H A D | qcom-apq8026-asus-sparrow.dts | 250 qcom,fast-charge-safe-current = <1500000>;
252 qcom,fast-charge-safe-voltage = <4430000>;
|
| H A D | qcom-apq8026-lg-lenok.dts | 289 qcom,fast-charge-safe-current = <450000>;
291 qcom,fast-charge-safe-voltage = <4350000>;
|
| /openbmc/linux/drivers/mtd/devices/ |
| H A D | phram.c | 114 struct phram_mtd_list *this, *safe; in unregister_devices() local
116 list_for_each_entry_safe(this, safe, &phram_list, list) { in unregister_devices()
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | cross-thread-rsb.rst | 13 address prediction entries with safe targets when context switching to the idle
69 context switch fills the RAP entries (referred to as the RSB in Linux) with safe
|
| /openbmc/phosphor-fan-presence/docs/control/fanctl/ |
| H A D | README.md | 22 enabled yet, an intended safe fan target should be set prior to resuming.
50 algorithm enabled yet, an intended safe fan target should be set
|
| /openbmc/linux/drivers/net/can/spi/mcp251xfd/ |
| H A D | mcp251xfd-ring.c | 43 len += sizeof(write_reg_buf->safe.cmd); in mcp251xfd_cmd_prepare_write_reg()
44 crc = mcp251xfd_crc16_compute(&write_reg_buf->safe, len); in mcp251xfd_cmd_prepare_write_reg()
48 len += sizeof(write_reg_buf->safe.crc); in mcp251xfd_cmd_prepare_write_reg()
|
| /openbmc/openbmc/poky/meta/recipes-core/glibc/glibc/ |
| H A D | 0006-nativesdk-glibc-Allow-64-bit-atomics-for-x86.patch | 7 This should be safe for i586 and newer CPUs.
|
| /openbmc/linux/arch/arm/mach-davinci/ |
| H A D | Kconfig | 58 printed, it's safe to deselect DAVINCI_MUX for your product.
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | meson.build | 7 not cflag.contains('safe-stack') and not cflag.contains('cfi-icall')
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 70 when it is safe to do so, e.g. when the affected locks are released
73 The theory about how to apply functions a safe way is rather complex.
83 Patches are applied on a per-task basis, when the task is deemed safe to
95 safe to patch tasks:
184 klp_update_patch_state() in a safe location. Kthreads are typically
185 in an infinite loop which does some action repeatedly. The safe
194 There the safe location must be carefully selected on a case-by-case
388 Module removal is only safe when there are no users of functions provided
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gdb/gdb/ |
| H A D | 0007-Fix-invalid-sigprocmask-call.patch | 16 and this is how musl-libc is currently doing. Fix the call to be safe
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-lxml_5.1.0.bb | 3 libxslt libraries. It provides safe and convenient access to these \
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | rk3399-gru-kevin.dts | 166 /* These are relatively safe rise/fall times. */
182 /* These are relatively safe rise/fall times. */
|
| /openbmc/u-boot/doc/ |
| H A D | README.ublimage | 51 safe
53 MODE safe
|
| /openbmc/linux/lib/fonts/ |
| H A D | Kconfig | 22 If unsure, say N (the default choices are safe).
36 here is safe.
|
| /openbmc/linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3399-gru-kevin.dts | 185 /* These are relatively safe rise/fall times. */
201 /* These are relatively safe rise/fall times. */
|