Searched full:end (Results 1 – 25 of 767) sorted by relevance
12345678910>>...31
| /Documentation/admin-guide/kdump/ |
| D | gdbmacros.txt | 32 end
34 end
46 end
48 end
50 end
52 end
53 end
56 end
75 end
76 end
[all …]
|
| /Documentation/networking/ |
| D | mac80211-auth-assoc-deauth.txt | 23 end note
24 end
33 end
41 end
46 end
51 end
58 end
66 end
79 end note
82 end
|
| /Documentation/translations/zh_CN/core-api/ |
| D | cachetlb.rst | 55 unsigned long start, unsigned long end)``
58 这个接口必须确保以前对‘start’到‘end-1’范围内的地址空间‘vma->vm_mm’
60 ‘mm’的页表项用于‘start’到‘end-1’范围内的虚拟地址。
99 2) flush_cache_range(vma, start, end);
100 change_range_of_page_tables(mm, start, end);
101 flush_tlb_range(vma, start, end);
138 unsigned long start, unsigned long end)``
141 后，在“start”到“end-1”范围内的虚拟地址的“vma->vm_mm”的缓存中
176 6) ``void flush_cache_vmap(unsigned long start, unsigned long end)``
177 ``void flush_cache_vunmap(unsigned long start, unsigned long end)``
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-pisp-be.rst | 9 Raspberry Pi PiSP Back End configuration format
12 The Raspberry Pi PiSP Back End memory-to-memory image signal processor is
17 The PiSP Back End processes images in tiles, and its configuration requires
23 provide detailed description of the ISP back end configuration and programming
48 Raspberry Pi PiSP Back End uAPI data types
52 PiSP Back End. The section is informative only, for a detailed description of
|
| D | constraints.svg | 9 …end="url(#Arrow2Mend)" stroke="#000080" stroke-linejoin="round" stroke-width="99.991"/><rect id="r…
10 …end="url(#marker5469)" stroke="#000080" stroke-linejoin="round" stroke-width="100"/><rect id="rect…
11 fill="none"/><path id="path319" d="m9650 12550v1505.2" fill="none" marker-end="url(#marker5693)" st…
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-memmap | 40 end The end address, inclusive (regardless whether the
49 /sys/firmware/memmap/0/end
72 end=$(cat $dir/end)
74 printf "%016x-%016x (%s)\n" $start $[ $end +1] "$type"
|
| D | configfs-usb-gadget-ecm | 14 - MAC address of host's end of this
17 - MAC address of device's end of this
|
| D | configfs-usb-gadget-ncm | 11 host_addr - MAC address of host's end of this
13 dev_addr - MAC address of device's end of this
|
| D | configfs-usb-gadget-eem | 12 host_addr MAC address of host's end of this
14 dev_addr MAC address of device's end of this
|
| D | configfs-usb-gadget-subset | 12 host_addr MAC address of host's end of this
14 dev_addr MAC address of device's end of this
|
| D | configfs-usb-gadget-rndis | 12 host_addr MAC address of host's end of this
14 dev_addr MAC address of device's end of this
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | partition.yaml | 89 assembled), the end result is that the entry ends with the padding
93 align-end:
99 This sets the alignment (in bytes) of the end of an entry with respect
102 Some entries require that they end on an alignment boundary,
105 But there may be padding at the end. While this does not affect the
107 parent section is assembled), the end result is that the entry ends
108 with the padding bytes, so may grow. If ‘align-end’ is not provided,
133 align-end = <0x10000>;
|
| /Documentation/admin-guide/aoe/ |
| D | status.sh | 21 for d in `ls -d $sysd/block/etherd* 2>/dev/null | grep -v p` end; do
22 # maybe ls comes up empty, so we use "end"
23 test $d = end && continue
|
| /Documentation/admin-guide/ |
| D | pstore-blk.rst | 78 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4.
81 There are multiple chunks for oops/panic front-end depending on the remaining
90 The chunk size in KB for pmsg front-end. It **MUST** be a multiple of 4.
93 Unlike oops/panic front-end, there is only one chunk for pmsg front-end.
102 The chunk size in KB for console front-end. It **MUST** be a multiple of 4.
105 Similar to pmsg front-end, there is only one chunk for console front-end.
113 The chunk size in KB for ftrace front-end. It **MUST** be a multiple of 4.
116 Similar to oops front-end, there are multiple chunks for ftrace front-end
186 files is ``dmesg-pstore-blk-[N]`` for oops/panic front-end,
187 ``pmsg-pstore-blk-0`` for pmsg front-end and so on. The timestamp of the
|
| /Documentation/core-api/ |
| D | asm-annotations.rst | 23 developers have been using ``ENTRY``, ``END``, ``ENDPROC``, and other
27 ``END`` used to mark the end of data or end of special functions with
61 There was a discussion_ and instead of extending the current ``ENTRY/END*``
80 save/restore of frame pointer shall happen at the start/end of a function,
107 denoting a range of code via ``SYM_*_START/END`` annotations.
159 ``END``. Except ``END`` had several other meanings too.
186 ``SYM_DATA_END_LABEL``. The latter adds also a label to the end, so that
200 In the end, they expand to ``SYM_DATA_START`` with ``SYM_DATA_END``
|
| D | cachetlb.rst | 54 unsigned long start, unsigned long end)``
60 'start' to 'end-1' will be visible to the cpu. That is, after
62 virtual addresses in the range 'start' to 'end-1'.
95 At the end of every page fault, this routine is invoked to tell
116 2) flush_cache_range(vma, start, end);
117 change_range_of_page_tables(mm, start, end);
118 flush_tlb_range(vma, start, end);
163 unsigned long start, unsigned long end)``
168 the range 'start' to 'end-1'.
212 6) ``void flush_cache_vmap(unsigned long start, unsigned long end)``
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | nxp,imx93-adc.yaml | 31 - description: normal conversion, include EOC (End of Conversion),
32 ECH (End of Chain), JEOC (End of Injected Conversion) and
33 JECH (End of injected Chain).
|
| /Documentation/maintainer/ |
| D | messy-diffstat.rst | 31 "subtract" the beginning point from the end point and display the resulting
56 for cN may end up being messy indeed, and developers often end up wondering
59 What is happening here is that there are no longer two clear end points for
63 starts at vN-rc1, it may end up including all of the changes between there
64 and the second origin end point (vN-rc2), which is certainly not what our
72 end of that pull request; rebasing and/or merging just before pushing
|
| /Documentation/netlink/ |
| D | netlink-raw.yaml | 36 # End netlink-raw
56 # End genetlink-c
63 # End genetlink-legacy
116 # End genetlink-c
172 # End genetlink-legacy
210 # End genetlink-c
284 # End genetlink-c
289 # End genetlink-legacy
300 # End netlink-raw
358 # End netlink-raw
[all …]
|
| D | genetlink-legacy.yaml | 56 # End genetlink-c
67 # End genetlink-legacy
120 # End genetlink-c
151 # End genetlink-legacy
189 # End genetlink-c
265 # End genetlink-c
270 # End genetlink-legacy
330 # End genetlink-legacy
370 # End genetlink-legacy
394 # End genetlink-legacy
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | richtek,rt9455.yaml | 29 richtek,end-of-charge-percentage:
33 below output_charge_current x end-of-charge-percentage, charge is terminated.
62 - richtek,end-of-charge-percentage
83 richtek,end-of-charge-percentage = <10>;
|
| /Documentation/admin-guide/media/ |
| D | raspberrypi-pisp-be.rst | 4 Raspberry Pi PiSP Back End Memory-to-Memory ISP (pisp-be)
7 The PiSP Back End
10 The PiSP Back End is a memory-to-memory Image Signal Processor (ISP) which reads
18 The PiSP Back End ISP processes images in tiles. The handling of image
25 in DRAM memory and processing them in the PiSP Back End to obtain images usable
32 The Raspberry Pi PiSP Back End (pisp-be) driver is located under
|
| /Documentation/accounting/ |
| D | taskstats-struct.rst | 20 /* Delay accounting fields end */
30 /* Extended accounting fields end */
40 Future extension should add fields to the end of the taskstats struct, and
101 * All values, until the comment "Delay accounting fields end" are
145 /* Delay accounting fields end */
155 * a tick is charged to a task's system time. So, at the end we
178 /* Extended accounting fields end */
|
| /Documentation/RCU/ |
| D | rculist_nulls.rst | 90 object has moved to the end of a new list, the traversal will not
92 be on the end of the new list and there's not a way to tell it's on a
110 * not in the middle or end.
125 very very fast (before the end of RCU grace period)
146 end-of-list marker for each slot of the hash table, we can detect
149 the lookup met the end of chain. If final 'nulls' value
182 // If the nulls value we got at the end of this lookup is
205 * not in the middle or end.
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 47 test, or an end-to-end test.
61 - An end-to-end test usually tests the entire system from the perspective of the
62 code under test. For example, someone might write an end-to-end test for the
|
12345678910>>...31
