Searched full:re (Results 1 – 25 of 484) sorted by relevance
12345678910>>...20
| /Documentation/sphinx/ |
| D | automarkup.py | 11 import re
15 # Python 2 lacks re.ASCII...
18 ascii_p3 = re.ASCII
29 RE_function = re.compile(r'\b(([a-zA-Z_]\w+)\(\))', flags=ascii_p3)
34 RE_generic_type = re.compile(r'\b(struct|union|enum|typedef)\s+([a-zA-Z_]\w+)',
41 RE_struct = re.compile(r'\b(struct)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
42 RE_union = re.compile(r'\b(union)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
43 RE_enum = re.compile(r'\b(enum)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
44 RE_typedef = re.compile(r'\b(typedef)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
50 RE_doc = re.compile(r'(\bDocumentation/)?((\.\./)*[\w\-/]+)\.(rst|txt)')
[all …]
|
| D | maintainers_include.py | 21 import re
73 if re.search('^[A-Z0-9]', line):
81 m = re.search(pat, line)
84 line = re.sub(pat, ':doc:`%s <../%s>`' % (m.group(2), m.group(2)), line)
93 m = re.search(r"\s(\S):\s", line)
97 m = re.search(r"\*([^\*]+)\*", line)
115 heading = re.sub(r"\s+", " ", line)
146 # Re-split on any added newlines in any above parsing.
|
| D | cdomain.py | 44 import re
58 RE_namespace = re.compile(r'^\s*..\s*c:namespace::\s*(\S+)\s*$')
70 RE_macro = re.compile(r'^\s*..\s*c:macro::\s*(\S+)\s+(\S.*)\s*$')
78 RE_ctype = re.compile(r'^\s*..\s*c:(struct|union|enum|enumerator|alias)::\s*(.*)$')
87 RE_ctype_refs = re.compile(r':c:(var|struct|union|enum|enumerator)::`([^\`]+)`')
94 RE_expr = re.compile(r':c:(expr|texpr):`([^\`]+)`')
116 n = n[:m.start()] + markup_func[m.re](m) + n[m.end():]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-request-ioc-reinit.rst | 13 MEDIA_REQUEST_IOC_REINIT - Re-initialize a request
32 this request ioctl can be used to re-initialize a previously allocated
35 Re-initializing a request will clear any existing data from the request.
38 be re-initialized and it is ready to be used again.
40 A request can only be re-initialized if it either has not been queued
|
| /Documentation/process/ |
| D | management-style.rst | 20 budget of your group, you're almost certainly not a kernel manager.
44 to decide on this", you're in trouble as a manager. The people you
46 you for a technical decision, you're screwed. You're clearly not
50 you, you're also screwed, although for a totally different reason.
56 makes you look like you know what you're doing, so what a kernel manager
77 fairly easy to backtrack. Since you're not going to be able to waste
81 incompetent nincompoop, say you're sorry, and undo all the worthless
160 "you're a d*ckhead" in millions of different ways [#f2]_, sometimes without
179 frankly, "A Million Ways to Tell a Developer They're a D*ckhead" doesn't
188 knowledge that we're better than the average person (let's face it,
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | mmp.rst | 19 While the filesystem is live, the kernel sets up a timer to re-check the
20 MMP block at the specified MMP check interval. To perform the re-check,
21 the MMP sequence number is re-read; if it does not match the in-memory
25 memory and on disk, and the re-check is complete.
65 - The MMP re-check interval, in seconds.
|
| /Documentation/trace/postprocess/ |
| D | decode_msr.py | 5 import re
11 m = re.match(r'#define (MSR_\w+)\s+(0x[0-9a-fA-F]+)', j)
22 m = re.search(r'(read|write)_msr:\s+([0-9a-f]+)', j)
|
| /Documentation/bpf/ |
| D | llvm_reloc.rst | 244 .. _btf-co-re-relocations:
247 CO-RE Relocations
250 From object file point of view CO-RE mechanism is implemented as a set
251 of CO-RE specific relocation records. These relocation records are not
256 CO-RE relocations are applied to BPF instructions to update immediate
269 There are several kinds of CO-RE relocations that could be split in
347 CO-RE Relocation Record
414 CO-RE Relocation Examples
457 00: CO-RE <byte_off> [2] struct foo::a (0:0)
460 10: CO-RE <byte_off> [2] struct foo::a (0:0)
[all …]
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 26 you're not sure if it can happen and not sure how to handle it yet - make it a
32 are logically impossible. (Or, make them debug mode assertions if they're
34 we're not stuck debugging undefined behaviour should it turn out that you were
66 Whenever we're debugging, and the solution isn't immediately obvious, if the
77 everywhere. Having functions to print whatever object you're working with will
90 Tracepoints shouldn't be the first thing you reach for. They're an important
92 have to rely on tracing, we have to know which tracepoints we're looking for,
97 The humble counter is an incredibly useful tool. They're cheap and simple to
113 what you're doing you'll be amazed at how patient they're happy to be. Users
|
| /Documentation/arch/arm/ |
| D | interrupts.rst | 33 exclusive of each other - if you're processing one interrupt from the
71 * Re-run the IRQ
88 - optional. Not required if you're using do_level_IRQ for all
89 IRQs that use this 'irqchip'. Generally expected to re-trigger
154 acknowledge the SA1110 IRQ each time you re-read the SA1111 IRQ status.
161 be re-checked for pending events. (see the Neponset IRQ handler for
|
| /Documentation/networking/devlink/ |
| D | devlink-reload.rst | 23 - Devlink driver entities re-initialization, including applying
30 Other devlink entities may stay over the re-initialization:
81 # Run reload command for devlink driver entities re-initialization:
|
| /Documentation/driver-api/fpga/ |
| D | fpga-programming.rst | 19 * re-enable the bridges
52 * Indicate where the FPGA image is. This is pseudo-code; you're
75 /* Deallocate the image info if you're done with it */
|
| /Documentation/arch/parisc/ |
| D | debugging.rst | 43 where exactly it happened. If you're lucky the IAOQ will point to the
44 instruction that cleared the Q bit, if you're not it points anywhere
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 163 re-submitted to this queue due to timeouts or NAK packets sent by the EC.
174 re-submitted due to a packet acknowledgment timeout or NAK. On such a
175 re-submission, packets are not removed from the pending set.
209 well as initiating re-submission of all currently pending packets on
210 receival of a NAK message (re-submission in case of a NAK is similar to
211 re-submission due to timeout, see below for more details on that). Note that
223 packets, started when the respective packet begins (re-)transmission (i.e.
225 thread). It is used to trigger re-submission or, when the number of tries
229 work item (re-)scheduled to run when the next packet is set to time out. The
231 exceeded the timeout and, if there are any remaining packets, re-schedules
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-fadump | 46 Kdump udev rule re-registers fadump on memory add/remove events,
48 kdump udev rule that fadump re-registration is not required on
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_overview.rst | 24 * Supports BPF CO-RE mechanism, enabling BPF developers to write portable
130 BPF CO-RE (Compile Once – Run Everywhere)
140 libbpf steps up the BPF program portability by supporting the BPF CO-RE concept.
141 BPF CO-RE brings together BTF type information, libbpf, and the compiler to
166 specific kernel on the host. BPF CO-RE concept thus eliminates overhead
172 ``task_struct`` using BPF CO-RE and libbf. The basic helper to read a field in a
173 CO-RE relocatable manner is ``bpf_core_read(dst, sz, src)``, which will read
|
| /Documentation/devicetree/bindings/mtd/ |
| D | fsmc-nand.txt | 15 byte 0 TCLR : CLE to RE delay in number of AHB clock cycles, only 4 bits
18 byte 1 TAR : ALE to RE delay, 4 bits are valid. Same format as TCLR.
|
| /Documentation/security/ |
| D | siphash.rst | 27 If you're not deriving your key from here, you're doing it wrong.
106 Read the SipHash paper if you're interested in learning more:
150 If you're not deriving your key from here, you're doing it wrong.
|
| /Documentation/arch/powerpc/ |
| D | ptrace.rst | 13 resources. Since we're extending, we're trying to create an interface
27 Since we're at it, we added other useful info that the kernel can return to
|
| /Documentation/staging/ |
| D | crc32.rst | 15 - We're working in binary, so the digits are only 0 and 1, and
23 CRC is written in hex with the most significant bit omitted. (If you're
29 order they're actually sent. For example, standard RS-232 serial is
43 the polynomial from the remainder and we're back to where we started,
56 But also notice how the next_input_bit() bits we're shifting into
|
| /Documentation/sound/soc/ |
| D | overview.rst | 18 machine specific code to re-route audio, enable amps, etc., after such an
54 multiple re-usable component drivers :-
|
| /Documentation/ |
| D | Kconfig | 19 described at Documentation/ABI/README. Yet, as they're manually
|
| /Documentation/admin-guide/blockdev/ |
| D | zram.rst | 50 -EAGAIN re-try operation later (e.g. when attempting to run recompress
496 It is also possible to limit the number of pages zram re-compression will
503 During re-compression for every page, that matches re-compression criteria,
505 order of their priorities. ZRAM stops either when re-compression was
506 successful (re-compressed object is smaller in size than the original one)
507 and matches re-compression criteria (e.g. size threshold) or when there are
509 successfully re-compressed the page such a page is marked as incompressible,
510 so ZRAM will not attempt to re-compress it in the future.
512 This re-compression behaviour, when it iterates through the list of
|
| /Documentation/filesystems/nfs/ |
| D | reexport.rst | 89 you're unlikely to have trouble using NFSv4 to reexport any filesystem
91 something that also supports NFSv3, you're *probably* OK. Re-exporting
|
| /Documentation/PCI/ |
| D | pci-error-recovery.rst | 42 of reset it desires, the choices being a simple re-enabling of I/O
47 After a reset and/or a re-enabling of I/O, all drivers are
159 then the platform should re-enable IOs on the slot (or do nothing in
190 The platform re-enables MMIO to the device (but typically not the
200 link reset was performed by the HW. If the platform can't just re-enable IOs
211 such an error might cause IOs to be re-blocked for the whole
284 This call gives drivers the chance to re-initialize the hardware
285 (re-download firmware, etc.). At this point, the driver may assume
|
12345678910>>...20