Searched full:harmful (Results 1 – 25 of 28) sorted by relevance
12
59 volatile-considered-harmful
7 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
85 volatile-considered-harmful
5 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
52 offensive, or harmful.
49 volatile-considered-harmful
11 Linux kernel module or driver to be harmful and undesirable. We have
50 unnecessary - and potentially harmful.
82 just as harmful as premature optimization. Abstraction should be used to
54 volatile-considered-harmful
3 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst <volatile_considered_harmful…
52 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
121 // caller must fix the bug. Sleeping here is intentional and less harmful in drop()
56 * decrements are not harmful as the reference count still stays in the
148 patched state. This may be harmful to the system though. Sending a fake signal
905 * the hope that the core is doing nothing harmful & in cps_cleanup_dead_cpu()
627 * harmful in general. in dma_get_required_mask()
363 * waiting too long would be harmful to the system, e.g. during SE reboot.
891 * because that can cause harmful races, if poll has already in tsi108_rx_int()
1326 * coherent, and potentially harmful in certain situations (PCIe/PL310
1290 * is both useless and harmful: later read-modify-write updates would in tas_update_status()
1751 * are potentially harmful to system integrity, and thus should only
169 * which is considered harmful (RFC-8021). Avoid that. in ip6_finish_output_gso_slowpath_drop()
811 ** isn't harmful. in lba_fixup_bus()
313 * not terribly harmful) in emac_netif_start()