Searched full:case (Results  1 – 25 of 1326) sorted by relevance
12345678910>>...54
| /Documentation/userspace-api/media/v4l/ | 
| D | capture.c.rst | 90 	    case IO_METHOD_READ: 93 			    case EAGAIN: 96 			    case EIO: 109 	    case IO_METHOD_MMAP: 117 			    case EAGAIN: 120 			    case EIO: 138 	    case IO_METHOD_USERPTR: 146 			    case EAGAIN: 149 			    case EIO: 220 	    case IO_METHOD_READ: [all …] 
 | 
| /Documentation/admin-guide/mm/ | 
| D | nommu-mmap.rst | 17 and it's also much more restricted in the latter case: 21 	In the MMU case: VM regions backed by arbitrary pages; copy-on-write 24 	In the no-MMU case: VM regions backed by arbitrary contiguous runs of 30 	shared across fork() or clone() without CLONE_VM in the MMU case. Since 31 	the no-MMU case doesn't support these, behaviour is identical to 36 	In the MMU case: VM regions backed by pages read from file; changes to 39 	In the no-MMU case: 61 	In the MMU case: like the non-PROT_WRITE case, except that the pages in 66 	In the no-MMU case: works much like the non-PROT_WRITE case, except 71 	In the MMU case: VM regions backed by pages read from file; changes to [all …] 
 | 
| /Documentation/usb/ | 
| D | mtouchusb.rst | 32         USB Capacitive - Pearl Case     14-205  (Discontinued) 33         USB Capacitive - Black Case     14-124  (Discontinued) 34         USB Capacitive - No Case        14-206  (Discontinued) 36         USB Capacitive - Pearl Case     EXII-5010UC 37         USB Capacitive - Black Case     EXII-5030UC 38         USB Capacitive - No Case        EXII-5050UC
  | 
| D | usbdevfs-drop-permissions.c | 92 		case 0:  in main() 94 		case 1:  in main() 97 		case 2:  in main() 100 		case 3:  in main()
  | 
| /Documentation/arch/x86/ | 
| D | tsx_async_abort.rst | 13 case certain loads may speculatively pass invalid data to dependent operations 70 …0          0           1        Invalid case   Invalid case       Invalid case          Invalid ca… 85 …0          0           1        Invalid case   Invalid case       Invalid case         Invalid case 100 …0          0           1        Invalid case  Invalid case        Invalid case          Invalid ca…
  | 
| /Documentation/admin-guide/ | 
| D | java.rst | 56    following (this is because Java is broken in case of the filename 255 	case CP_UTF8: 259 	case CP_CLASS: 260 	case CP_STRING: 261 	case CP_METHODTYPE: 264 	case CP_METHODHANDLE: 267 	case CP_INTEGER: 268 	case CP_FLOAT: 269 	case CP_FIELDREF: 270 	case CP_METHODREF: [all …] 
 | 
| D | bug-bisect.rst | 64    minutes more on testing in case your reproducer is unreliable. 68    test after this (roughly 10 steps)'. In that case go back to step 1. 71    is the first bad commit', then you have finished the bisection. In that case 77    In case you missed Git's output, you can always run ``git bisect log`` to 90   codebase and check if that fixes your bug; if that is the case, it validates 100   commit. In that case, abandon the attempt. Do the same, if Git fails to revert 102   you bisected a stable or longterm kernel series, in which case you want to
  | 
| /Documentation/block/ | 
| D | ioprio.rst | 120 		case 'n': 124 		case 'c': 128 		case 'p': 135 		case IOPRIO_CLASS_NONE: 138 		case IOPRIO_CLASS_RT: 139 		case IOPRIO_CLASS_BE: 141 		case IOPRIO_CLASS_IDLE:
  | 
| /Documentation/bpf/ | 
| D | map_queue_stack.rst | 43 negative error in case of failure. 53 removing it. Returns ``0`` on success, or negative error in case of 64 stack. Returns ``0`` on success, or negative error in case of failure. 81 success, or negative error in case of failure. 92 set to ``NULL``.  Returns ``0`` on success, or negative error in case of 104 must be set to ``NULL``. Returns ``0`` on success, or negative error in case of
  | 
| /Documentation/core-api/ | 
| D | pin_user_pages.rst | 48 FOLL_LONGTERM is a specific case, more restrictive case of FOLL_PIN. 131 CASE 1: Direct IO (DIO) 143 CASE 2: RDMA 156 .. _mmu-notifier-registration-case: 158 CASE 3: MMU notifier registration, with or without page faulting hardware 175 CASE 4: Pinning for struct page manipulation only 181 CASE 5: Pinning in order to write to the data within the page 183 Even though neither DMA nor Direct IO is involved, just a simple case of "pin, 184 write to a page's data, unpin" can cause a problem. Case 5 may be considered a 185 superset of Case 1, plus Case 2, plus anything that invokes that pattern. In [all …] 
 | 
| D | refcount-vs-atomic.rst | 76 case 1) - non-"Read/Modify/Write" (RMW) ops 89 case 2) - non-"Read/Modify/Write" (RMW) ops with release ordering 101 case 3) - increment-based ops that return no value 113 case 4) - decrement-based RMW ops that return no value 125 case 5) - increment-based RMW ops that return a value 141 case 6) - increment-based RMW ops with acquire ordering that return a value 154 case 7) - generic dec/sub decrement-based RMW ops that return a value 167 case 8) other decrement-based RMW ops that return a value 182 case 9) - lock-based RMW
  | 
| /Documentation/filesystems/ext4/ | 
| D | orphan.rst | 7 are still alive because they are open. In case of crash the filesystem has to 10 to perform the operation in a single journalling transaction. In such case we 11 track the inode as orphan so that in case of crash extra blocks allocated to 38 be valid orphan entries. In case we see this feature when mounting the
  | 
| /Documentation/networking/ | 
| D | 6lowpan.rst | 37  case ARPHRD_6LOWPAN: 41 	case LOWPAN_LLTYPE_FOOBAR: 51 In case of generic 6lowpan branch ("net/6lowpan") you can remove the check
  | 
| D | seg6-sysctl.rst | 30 	IPv6 header in case of SR T.encaps 34 	  0  copy flowlabel from Inner packet in case of Inner IPv6 35 	     (Set flowlabel to 0 in case IPv4/L2)
  | 
| /Documentation/ABI/stable/ | 
| D | sysfs-hypervisor-xen | 7 		Might return "<denied>" in case of special security settings 16 		Might return "<denied>" in case of special security settings 25 		Might return "<denied>" in case of special security settings 56 		Might return "<denied>" in case of special security settings 73 		Might return "0" in case of special security settings 105 		Might return "<denied>" in case of special security settings
  | 
| /Documentation/devicetree/bindings/net/ | 
| D | mediatek-dwmac.yaml | 112       1. tx clock will be inversed in MII/RGMII case, 114          which is from external PHYs in RMII case, and it rarely happen. 115       3. the reference clock, which outputs to TXC pin will be inversed in RMII case 122       1. rx clock will be inversed in MII/RGMII case. 123       2. reference clock will be inversed when arrived at MAC in RMII case, when 125       3. the inside clock, which be sent to MAC, will be inversed in RMII case when
  | 
| /Documentation/ABI/testing/ | 
| D | sysfs-class-mtd | 43 		<major>:<minor> format).  In this case <minor> will be odd. 117 		In the case of NOR flash it is 1 (even though individual 120 		In the case of NAND flash it is one NAND page (or a 123 		In the case of ECC NOR, it is the ECC block size. 134 		In the case of devices lacking any ECC capability, it is 0. 185 		It will always be a non-negative integer.  In the case of 196 		It will always be a non-negative integer.  In the case of 207 		It will always be a non-negative integer.  In the case of
  | 
| D | sysfs-bus-event_source-devices-events | 40 		As performance monitoring event names are case 42 		for lower or upper case event names in sysfs to avoid 44 		name of the event here is either lower or upper case. 68 		In the case of the last example, a value replacing "?" would
  | 
| /Documentation/dev-tools/kunit/ | 
| D | architecture.rst | 26 The test case is the fundamental unit in KUnit. KUnit test cases are organised 27 into suites. A KUnit test case is a function with type signature 28 ``void (*)(struct kunit *test)``. These test case functions are wrapped in a 34 Each KUnit test case receives a ``struct kunit`` context object that tracks a 101 or parts of the kernel, each KUnit case executes in a separate thread 118 	- Failing assertions, on the other hand, result in the test case being 151 The test case includes a KUNIT_CASE_PARAM() macro that accepts a 154 array-based common-case generators.
  | 
| /Documentation/mm/ | 
| D | hugetlbfs_reserv.rst | 118 be used to specify the offset into the underlying file.  In such a case, 166 modified to reflect the reservations.  In the case of a shared mapping, a 191 specified address.  The avoid_reserve argument is most often used in the case 204 However, in every case the avoid_reserve argument overrides the use of 277 be the case if the page was associated with a subpool that contained 291 Therefore, the global resv_huge_pages counter is incremented in this case. 337 biggest reservation concern for COW is private mappings.  In this case, 354 In the case where the faulting task is not the owner, the fault will fail and 407 return value of region_chg().  However, in the case of shared mappings it is 409 region_chg() and region_add().  In this case, the return value of region_add() [all …] 
 | 
| /Documentation/devicetree/bindings/power/reset/ | 
| D | keystone-reset.txt | 3 This node is intended to allow SoC reset in case of software reset 37 Setup keystone reset so that in case software reset or 58 Setup keystone reset so that in case of software reset or
  | 
| /Documentation/devicetree/bindings/mtd/ | 
| D | nand-chip.yaml | 30       case the phandle should reference the parent node. 32       case the phandle should reference the node itself. 33       3/ The ECC engine is external, in this case the phandle should
  | 
| /Documentation/devicetree/bindings/usb/ | 
| D | mediatek,mtk-xhci.yaml | 18   case 1: only supports xHCI driver; 19   case 2: supports dual-role mode, and the host is based on xHCI driver. 22   # common properties for both case 1 and case 2 52       - const: ippc  # optional, only needed for case 1. 139   # the following properties are only used for case 1
  | 
| /Documentation/core-api/irq/ | 
| D | concepts.rst | 17 all of the interrupt controller in the system.  In the case of ISA 22 are encouraged to in the case  where there is any manual configuration
  | 
| /Documentation/translations/zh_CN/process/ | 
| D | coding-style.rst | 49 在 switch 语句中消除多级缩进的首选的方式是让 ``switch`` 和从属于它的 ``case`` 50 标签对齐于同一列,而不要 ``两次缩进`` ``case`` 标签。比如: 55 	case 'G': 56 	case 'g': 59 	case 'M': 60 	case 'm': 63 	case 'K': 64 	case 'k': 139 	case KOBJ_ADD: 141 	case KOBJ_REMOVE: [all …] 
 | 
        12345678910>>...54