Searched refs:WHAT (Results 1 – 11 of 11) sorted by relevance
| /linux-6.12.1/drivers/md/dm-vdo/ |
| D | memory-alloc.h | 70 #define vdo_allocate(COUNT, TYPE, WHAT, PTR) \ argument
71 __vdo_do_allocation(COUNT, sizeof(TYPE), 0, __alignof__(TYPE), WHAT, PTR)
86 #define vdo_allocate_extended(TYPE1, COUNT, TYPE2, WHAT, PTR) \ argument
95 WHAT, \
|
| /linux-6.12.1/drivers/iommu/amd/ |
| D | Kconfig | 35 DO NOT ENABLE THIS OPTION UNLESS YOU REALLY, -REALLY- KNOW WHAT YOU ARE DOING!!!
|
| /linux-6.12.1/drivers/iommu/intel/ |
| D | Kconfig | 41 DO NOT ENABLE THIS OPTION UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!!!
|
| /linux-6.12.1/Documentation/RCU/ |
| D | whatisRCU.rst | 39 :ref:`2. WHAT IS RCU'S CORE API? <2_whatisRCU>`
41 :ref:`3. WHAT ARE SOME EXAMPLE USES OF CORE RCU API? <3_whatisRCU>`
43 :ref:`4. WHAT IF MY UPDATING THREAD CANNOT BLOCK? <4_whatisRCU>`
45 :ref:`5. WHAT ARE SOME SIMPLE IMPLEMENTATIONS OF RCU? <5_whatisRCU>`
142 2. WHAT IS RCU'S CORE API?
433 3. WHAT ARE SOME EXAMPLE USES OF CORE RCU API?
526 4. WHAT IF MY UPDATING THREAD CANNOT BLOCK?
628 5. WHAT ARE SOME SIMPLE IMPLEMENTATIONS OF RCU?
|
| /linux-6.12.1/Documentation/i2c/busses/ |
| D | i2c-piix4.rst | 71 ABOUT WHAT YOU ARE DOING!
|
| /linux-6.12.1/arch/m68k/fpsp040/ |
| D | satan.S | 320 |--WHAT WE HAVE HERE IS MERELY A1 = A3, A2 = A1/A3, A3 = A2/A3.
|
| /linux-6.12.1/Documentation/admin-guide/laptops/ |
| D | sony-laptop.rst | 140 **I HAVE NO IDEA WHAT THOSE METHODS DO.**
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | f2fs.rst | 4 WHAT IS Flash-Friendly File System (F2FS)?
|
| /linux-6.12.1/Documentation/process/ |
| D | coding-style.rst | 606 Generally, you want your comments to tell WHAT your code does, not HOW.
|
| /linux-6.12.1/Documentation/ |
| D | memory-barriers.txt | 355 WHAT ARE MEMORY BARRIERS?
529 WHAT MAY NOT BE ASSUMED ABOUT MEMORY BARRIERS?
|
| /linux-6.12.1/arch/m68k/ifpsp060/src/ |
| D | fpsp.S | 6426 #--WHAT WE HAVE HERE IS MERELY A1 = A3, A2 = A1/A3, A3 = A2/A3.
|