Searched full:harmful (Results 1 – 25 of 39) sorted by relevance
12
56 volatile-considered-harmful
5 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
59 volatile-considered-harmful
7 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
60 volatile-considered-harmful
52 offensive, or harmful.
11 Linux kernel module or driver to be harmful and undesirable. We have
50 unnecessary - and potentially harmful.
78 just as harmful as premature optimization. Abstraction should be used to
3 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst <volatile_considered_harmful…
29 * into a control dependency and consequently allowing for harmful
38 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
20 different type. This prevents unpredictable, potentially harmful,
22 used in the system. Using another frequency may cause harmful effects
159 * being traced, the MOV is not harmful given x9 is not live per the AAPCS.
208 * method which should not be harmful. in rockchip_pcie_phy_power_on()
78 or may not be harmful to your hardware.. two or more cards driving the same IRQ
460 * writing this data shouldn't be harmful even in those cases.
574 * the hope that the core is doing nothing harmful & in cps_cpu_die()
148 patched state. This may be harmful to the system though. Sending a fake signal
486 * harmful in general. in dma_get_required_mask()
361 * waiting too long would be harmful to the system, e.g. during SE reboot.
935 * are potentially harmful to system integrity, and thus should only
227 be harmful. Namely, in that case the governor will select an idle state with
