| /openbmc/linux/Documentation/netlink/ |
| H A D | netlink-raw.yaml | 14 pattern: ^[0-9A-Za-z_]+( - 1)?$
|
| /openbmc/linux/drivers/video/fbdev/ |
| H A D | ffb.c | 318 u32 pattern[32]; member
|
| /openbmc/linux/Documentation/trace/ |
| H A D | kprobetrace.rst | 108 With 'symstr' type, you can filter the event with wildcard pattern of the
|
| H A D | ftrace-uses.rst | 254 match a specific pattern.
|
| /openbmc/linux/Documentation/networking/ |
| H A D | tls-offload.rst | 309 the device starts scanning for a known header pattern. For example
311 in the SSL/TLS version field of the header. Once pattern is matched
|
| /openbmc/linux/Documentation/driver-api/dmaengine/ |
| H A D | provider.rst | 201 - The device is able to fill memory with the provided pattern
203 - The pattern is treated as a single byte signed value.
|
| /openbmc/qemu/docs/about/ |
| H A D | emulation.rst | 579 access was. Not compatible with the pattern option. Example output::
586 * - pattern
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/ |
| H A D | qunit-1.18.0.js | 215 …function(text1,text2){var text1Length,text2Length,textLength,best,length,pattern,found;text1Length…
218 best=0;length=1;while(true){pattern=text1.substring(textLength-length);found=text2.indexOf(pattern)…
|
| /openbmc/entity-manager/ |
| H A D | Doxyfile | 928 # exclude all test directories for example use the pattern */test/*
939 # exclude all test directories use the pattern */test/*
950 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
990 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
991 # basis. Doxygen will compare the file name with each pattern and apply the
992 # filter if there is a match. The filters are a list of the form: pattern=filter
1011 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
1012 # it is also possible to disable source filtering for a specific pattern using
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 147 ``core_pattern`` is used to specify a core dumpfile pattern name.
150 * ``core_pattern`` is used as a pattern template for the output
183 * If the first character of the pattern is a '|', the kernel will treat
184 the rest of the pattern as a command to run. The core dump will be
|
| /openbmc/linux/Documentation/fb/ |
| H A D | framebuffer.rst | 160 the screen is covered by a pattern of colored phosphors (pixels). If a phosphor
|
| /openbmc/linux/Documentation/devicetree/bindings/iommu/ |
| H A D | arm,smmu.yaml | 23 pattern: "^iommu@[0-9a-f]*"
|
| /openbmc/linux/drivers/mtd/nand/raw/ |
| H A D | nand_base.c | 2509 const struct nand_op_parser_pattern *pattern; in nand_op_parser_exec_op() local
2516 pattern = &parser->patterns[i]; in nand_op_parser_exec_op()
2517 if (!nand_op_parser_match_pat(pattern, &test_ctx)) in nand_op_parser_exec_op()
2537 pattern = &parser->patterns[best_pattern]; in nand_op_parser_exec_op()
2538 ret = pattern->exec(chip, &ctx.subop); in nand_op_parser_exec_op()
|
| /openbmc/u-boot/tools/binman/ |
| H A D | README.entries | 78 - pattern: Filename pattern to match the files to include
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | zonefs.rst | 145 write pattern, zonefs prevents buffered writes and writeable shared mappings
178 failure pattern, the standards governing zoned block devices behavior define
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | ice.rst | 215 two-byte pattern and offset by using the ethtool user-def and mask fields. Only
274 To set a filter based on a user-defined pattern and offset::
280 the pattern (0xffff).
|
| /openbmc/linux/Documentation/arch/arm/omap/ |
| H A D | dss.rst | 332 - Draw test pattern to framebuffer whenever framebuffer settings change.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | pin_user_pages.rst | 183 superset of Case 1, plus Case 2, plus anything that invokes that pattern. In
|
| /openbmc/docs/designs/ |
| H A D | expired-password.md | 143 terminate the session. The usage pattern is:
|
| H A D | redfish-spdm-attestation.md | 226 constructs cert path following the pattern
|
| /openbmc/qemu/docs/devel/ |
| H A D | qom.rst | 308 A lot of the code outlined above follows a standard pattern and naming
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 156 Another lockless design pattern that has been baked into an API
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | writing_usb_driver.rst | 140 pattern that your driver registered with the USB core, the probe
|
| /openbmc/linux/Documentation/security/keys/ |
| H A D | trusted-encrypted.rst | 391 binary pattern at offset 3 in the key. The OIDs currently made
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/engine/disp/ |
| H A D | gv100.c | 92 .pattern = gm107_sor_dp_pattern,
|