/openbmc/linux/Documentation/power/regulator/ |
H A D | design.rst | 11 - Errors in regulator configuration can have very serious consequences
|
/openbmc/openbmc/poky/meta/recipes-multimedia/libvorbis/libvorbis/ |
H A D | 0001-configure-Check-for-clang.patch | 52 # glibc < 2.1.3 has a serious FP bug in the math inline header
|
/openbmc/linux/Documentation/admin-guide/blockdev/drbd/ |
H A D | drbd-connection-state-overview.dot | 61 Unconnected -> StandAlone [ label="drbdadm disconnect\lor serious communication trouble" ]
|
/openbmc/u-boot/doc/ |
H A D | I2C_Edge_Conditions | 42 Many thanks to Bill Hunter for finding this serious BUG.
|
H A D | README.memory-test | 27 There are a number of serious problems with this command:
|
/openbmc/qemu/ |
H A D | qemu.sasl | 12 # QEMU VNC. Per RFC 6331 this is vulnerable to many serious security
|
/openbmc/linux/Documentation/arch/arm/nwfpe/ |
H A D | notes.rst | 8 I also found one oddity in the emulator. I don't think it is serious but
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/trusted-services/corstone1000/ |
H A D | 0013-Fix-error-handling-of-variable-index-loading.patch | 7 will silently continue with empty variable store. This is a serious
|
/openbmc/u-boot/arch/arm/mach-aspeed/ |
H A D | Kconfig | 66 WARNING: this has serious security implications: it grants
|
/openbmc/qemu/docs/devel/ |
H A D | conflict-resolution.rst | 8 serious code of conduct violations (including sexist/racist statements
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | dm-init.rst | 40 Not all target types are available as there are serious risks in allowing
|
/openbmc/linux/Documentation/networking/ |
H A D | tproxy.rst | 59 usually done with the iptables REDIRECT target; however, there are serious
|
/openbmc/linux/Documentation/RCU/ |
H A D | lockdep-splat.rst | 16 This problem can therefore be serious: it might result in random memory
|
/openbmc/linux/Documentation/driver-api/acpi/ |
H A D | scan_handlers.rst | 68 the namespace scan should be terminated due to a serious error. The error code
|
/openbmc/linux/Documentation/process/ |
H A D | 3.Early-stage.rst | 213 on the assumption that they will be able to avoid serious integration 222 This kind of review is often enough to avoid serious problems later on
|
/openbmc/linux/arch/arm/boot/dts/rockchip/ |
H A D | rk3288-veyron-mickey.dts | 112 * some pretty serious workload here and be happy.
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | rk3288-veyron-mickey.dts | 137 * some pretty serious workload here and be happy.
|
/openbmc/linux/Documentation/power/ |
H A D | basic-pm-debugging.rst | 149 the problem is most probably hardware-related and serious, so it should be 154 indicates a serious problem that very well may be related to the hardware, but
|
/openbmc/linux/fs/befs/ |
H A D | ChangeLog | 55 for reporting this serious bug!!! 217 I've done some serious testing on it now (on my box anyhow), and it
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | securing-images.rst | 54 serious. Look for common web vulnerabilities such as
|
/openbmc/linux/Documentation/translations/zh_CN/kernel-hacking/ |
H A D | hacking.rst | 694 * give up. I'm serious, I am going to kick the living shit
|
/openbmc/qemu/docs/system/ |
H A D | vnc-security.rst | 170 multiple serious flaws described in detail in RFC 6331 and thus should
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | rtc.rst | 92 interrupts, so be aware of this if you are doing serious work. If you
|
/openbmc/linux/Documentation/dev-tools/kunit/ |
H A D | style.rst | 16 2. Writing tests which would cause serious problems if automatically run. For
|
/openbmc/linux/Documentation/dev-tools/ |
H A D | testing-overview.rst | 135 etc. Smatch also has tests against more serious issues such as integer
|