/linux-4.1.27/net/ipv4/netfilter/ |
D | nf_nat_snmp_basic.c | 588 union snmp_syntax syntax; member 629 int syntax; member 655 unsigned short *syntax) in snmp_tag_cls2syntax() argument 661 while (cnv->syntax != -1) { in snmp_tag_cls2syntax() 663 *syntax = cnv->syntax; in snmp_tag_cls2syntax() 728 (*obj)->syntax.l[0] = l; in snmp_object_decode() 742 memcpy((*obj)->syntax.c, p, len); in snmp_object_decode() 774 memcpy((*obj)->syntax.ul, lp, len); in snmp_object_decode() 793 memcpy((*obj)->syntax.uc, p, len); in snmp_object_decode() 809 (*obj)->syntax.ul[0] = ul; in snmp_object_decode()
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-probe.txt | 78 syntax is same as PROBE SYNTAX, but NO ARGs. 127 Probe points are defined by following syntax. 141 … the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is th… 146 Each probe argument follows below syntax. 158 Line range is described by following syntax. 164 probe syntax, 'SRC' means the source file path, 'ALN' is start line number,
|
/linux-4.1.27/ |
D | Kconfig | 2 # For a description of the syntax of this configuration file,
|
D | Kbuild | 8 # Default sed regexp - multiline due to syntax constraints
|
/linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
D | gpio-tz1090.txt | 20 - #gpio-cells: Should be 2. The syntax of the gpio specifier used by client 41 - #interrupt-cells: Should be 2. The syntax of the interrupt specifier used by
|
D | gpio-samsung.txt | 9 - #gpio-cells: Should be 4. The syntax of the gpio specifier used by client nodes
|
D | gpio-tz1090-pdc.txt | 11 - #gpio-cells: Should be 2. The syntax of the gpio specifier used by client
|
/linux-4.1.27/arch/microblaze/ |
D | Kconfig.debug | 1 # For a description of the syntax of this configuration file,
|
D | Kconfig.platform | 1 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/arch/powerpc/sysdev/ |
D | Kconfig | 1 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/arch/arm/include/asm/ |
D | unified.h | 24 .syntax unified
|
/linux-4.1.27/arch/x86/crypto/sha-mb/ |
D | sha1_mb_mgr_datastruct.S | 78 # Alternate "struc-like" syntax:
|
/linux-4.1.27/Documentation/devicetree/bindings/dma/ |
D | mpc512x-dma.txt | 13 - interrupt for the DMA controller: syntax of interrupt client node
|
/linux-4.1.27/Documentation/ |
D | bad_memory.txt | 31 boot-time. Its syntax is slightly strange and you may need to
|
D | serial-console.txt | 77 like this to /etc/inittab (exact syntax depends on your getty):
|
D | dynamic-debug-howto.txt | 48 If you make a mistake with the syntax, the write will fail thus: 236 the syntax described above, but must not exceed 1023 characters. Your
|
D | applying-patches.txt | 60 via stdin using the following syntax:
|
D | CodingStyle | 913 inside the block, and check it for correctness (syntax, types, symbol
|
D | kernel-parameters.txt | 144 Do not modify the syntax of boot loader parameters without extreme 763 in the running system. The syntax of range is
|
/linux-4.1.27/scripts/genksyms/ |
D | parse.tab.c_shipped | 726 number is the opposite. If YYTABLE_NINF, syntax error. */ 910 yyerror (YY_("syntax error: cannot back up")); \ 1282 case, just report a simple "syntax error". 1290 scanner and before detecting a syntax error. Thus, state merging 1337 YYCASE_(0, YY_("syntax error")); 1338 YYCASE_(1, YY_("syntax error, unexpected %s")); 1339 YYCASE_(2, YY_("syntax error, unexpected %s, expecting %s")); 1340 YYCASE_(3, YY_("syntax error, unexpected %s, expecting %s or %s")); 1341 YYCASE_(4, YY_("syntax error, unexpected %s, expecting %s or %s or %s")); 1342 YYCASE_(5, YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s")); [all …]
|
/linux-4.1.27/scripts/dtc/ |
D | dtc-parser.tab.c_shipped | 666 number is the opposite. If YYTABLE_NINF, syntax error. */ 770 yyerror (YY_("syntax error: cannot back up")); \ 1109 case, just report a simple "syntax error". 1117 scanner and before detecting a syntax error. Thus, state merging 1166 YYCASE_(0, YY_("syntax error")); 1167 YYCASE_(1, YY_("syntax error, unexpected %s")); 1168 YYCASE_(2, YY_("syntax error, unexpected %s, expecting %s")); 1169 YYCASE_(3, YY_("syntax error, unexpected %s, expecting %s or %s")); 1170 YYCASE_(4, YY_("syntax error, unexpected %s, expecting %s or %s or %s")); 1171 YYCASE_(5, YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s")); [all …]
|
/linux-4.1.27/Documentation/isdn/ |
D | README.act2000 | 45 loading the kernel with LILO or LOADLIN. It accepts the following syntax: 77 The following syntax is accepted:
|
D | README.icn | 71 loading the kernel with LILO or LOADLIN. It accepts the following syntax: 101 syntax is accepted:
|
D | README.HiSax | 497 Attention NEW VERSION, the old leased line syntax won't work !!!
|
/linux-4.1.27/scripts/kconfig/ |
D | zconf.tab.c_shipped | 697 number is the opposite. If YYTABLE_NINF, syntax error. */ 837 yyerror (YY_("syntax error: cannot back up")); \ 1207 case, just report a simple "syntax error". 1215 scanner and before detecting a syntax error. Thus, state merging 1262 YYCASE_(0, YY_("syntax error")); 1263 YYCASE_(1, YY_("syntax error, unexpected %s")); 1264 YYCASE_(2, YY_("syntax error, unexpected %s, expecting %s")); 1265 YYCASE_(3, YY_("syntax error, unexpected %s, expecting %s or %s")); 1266 YYCASE_(4, YY_("syntax error, unexpected %s, expecting %s or %s or %s")); 1267 YYCASE_(5, YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s")); [all …]
|
/linux-4.1.27/Documentation/device-mapper/ |
D | cache-policies.txt | 84 The syntax for a table is: 89 The syntax to send a message using the dmsetup command is:
|
/linux-4.1.27/Documentation/dvb/ |
D | get_dvb_firmware | 35 syntax() if (scalar(@ARGV) != 1); 54 syntax(); 934 sub syntax() { subroutine
|
/linux-4.1.27/Documentation/trace/ |
D | events.txt | 51 file. All of the events in a subsystem can be specified via the syntax 164 5.1 Expression syntax 321 The syntax for event triggers is roughly based on the syntax for 327 6.1 Expression syntax 343 The filter syntax is the same as that described in the 'Event
|
D | uprobetracer.txt | 56 offset, and container-size (usually 32). The syntax is;
|
D | kprobetrace.txt | 61 offset, and container-size (usually 32). The syntax is;
|
/linux-4.1.27/Documentation/blockdev/ |
D | cpqarray.txt | 89 10-28-2004 : General cleanup, syntax fixes for in-kernel driver version.
|
D | floppy.txt | 41 If you use the floppy driver as a module, use the following syntax:
|
/linux-4.1.27/Documentation/xtensa/ |
D | mmu.txt | 50 for details on the syntax and semantic of simple-bus nodes. The following
|
/linux-4.1.27/Documentation/kbuild/ |
D | kconfig-language.txt | 49 applicable everywhere (see syntax). 138 Various less common options can be defined via this option syntax, 170 module state. Dependency expressions have the following syntax: 249 Kconfig syntax
|
D | makefiles.txt | 45 === 7 Kbuild syntax for exported headers 115 kbuild infrastructure. This chapter introduces the syntax used in the 222 the syntax above will also work. So, if you have CONFIG_EXT2_FS=y, 395 This is a special rule, following the normal syntax 630 The syntax used to define composite objects for host programs is 631 similar to the syntax used for kernel objects. 644 Note: The syntax <executable>-y is not permitted for host-programs. 1145 LDFLAGS_$@ syntax - one for each potential target. 1237 See "7.4 generic-y" for further info on syntax etc. 1239 === 7 Kbuild syntax for exported headers [all …]
|
D | modules.txt | 164 NOTE: Further documentation describing the syntax used by kbuild is 445 The syntax of the Module.symvers file is:
|
/linux-4.1.27/Documentation/devicetree/bindings/mipi/dsi/ |
D | mipi-dsi-bus.txt | 6 define the syntax used to represent a DSI bus in a device tree.
|
/linux-4.1.27/Documentation/arm/nwfpe/ |
D | README.FPE | 26 Form 1 syntax: 31 Form 2 syntax:
|
/linux-4.1.27/arch/openrisc/ |
D | Kconfig | 2 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/Documentation/scsi/ |
D | tmscsim.txt | 220 to require all three to have a syntax similar to the output. 272 The syntax of the params is much shorter than the syntax of the /proc/... 280 Here's the syntax: 355 * More user friendly boot/module param syntax
|
D | scsi_fc_transport.txt | 303 The LLDD vport_create() syntax is: 376 The LLDD vport_disable() syntax is: 404 The LLDD vport_delete() syntax is:
|
D | st.txt | 265 also set using, e.g., the LILO command line. The preferred syntax is 271 For compatibility, the old syntax from early 2.5 and 2.4 kernel 280 The following syntax used by the old kernel versions is also supported:
|
D | ncr53c8xx.txt | 435 the proc SCSI file system. The generic command syntax is the 628 driver name "ncr53c8xx="(sym53c8xx). The kernel syntax parser then expects
|
D | ChangeLog.sym53c8xx | 428 and I just translated it into ncr53c8xx syntax.
|
D | sym53c8xx_2.txt | 296 the proc SCSI file system. The generic command syntax is the
|
D | ChangeLog.1992-1997 | 1925 verify_area syntax.
|
D | ChangeLog.lpfc | 1667 syntax checking
|
/linux-4.1.27/arch/c6x/ |
D | Kconfig | 2 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/Documentation/kdump/ |
D | kdump.txt | 47 when using the elfcorehdr=[size[KMG]@]offset[KMG] syntax. 252 Extended crashkernel syntax 255 While the "crashkernel=size[@offset]" syntax is sufficient for most 261 The syntax is:
|
/linux-4.1.27/Documentation/fb/ |
D | ep93xx-fb.txt | 104 The video mode is set using the following syntax:
|
/linux-4.1.27/drivers/auxdisplay/ |
D | Kconfig | 2 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/Documentation/video4linux/ |
D | meye.txt | 44 module argument syntax (<param>=<value> when passing the option to the
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | OSS-Emulation.txt | 32 /proc/asound/oss/sndstat. This shows in the same syntax of 126 The command sequence has the following syntax:
|
/linux-4.1.27/Documentation/networking/ |
D | eql.txt | 123 it in the routing table using the cool new route syntax that makes 142 The syntax for enslaving a device is "eql_enslave <master-name>
|
D | 3c509.txt | 42 needed except to enable full-duplex mode (see below). An example of the syntax
|
D | filter.txt | 154 covered by libpcap in high-level syntax, so as an application developer 174 previous section. Asm-like syntax mentioned here has been implemented in 176 less readable opcodes directly, principles are the same). The syntax is 200 and return instructions that are also represented in bpf_asm syntax. This
|
D | README.ipw2100 | 112 syntax:
|
D | README.sb1000 | 117 has no syntax errors and has the right nameserver IP addresses in it.
|
D | README.ipw2200 | 368 An Ad-Hoc networks is created using the syntax of the Wireless tool.
|
D | ixgb.txt | 107 this syntax:
|
D | bonding.txt | 1199 is the proper syntax to specify multiple targets. When specifying
|
/linux-4.1.27/drivers/firmware/ |
D | Kconfig | 2 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
D | renesas,pfc-pinctrl.txt | 88 The syntax of the gpio specifier used by client nodes should be the following
|
/linux-4.1.27/Documentation/filesystems/ |
D | ceph.txt | 69 The basic mount syntax is:
|
D | ubifs.txt | 99 The UBI volume to mount is specified using "ubiX_Y" or "ubiX:NAME" syntax,
|
/linux-4.1.27/drivers/parport/ |
D | Kconfig | 2 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/Documentation/laptops/ |
D | sonypi.txt | 48 module argument syntax (<param>=<value> when passing the option to the
|
D | asus-laptop.txt | 215 module argument syntax (<param>=<value> when passing the option to the
|
/linux-4.1.27/Documentation/input/ |
D | ff.txt | 82 Note: The exact syntax FF_CUSTOM is undefined for the time being as no driver
|
/linux-4.1.27/arch/m68k/ifpsp060/ |
D | TEST.DOC | 42 numbers are listed using the Motorola Assembly syntax assembler
|
/linux-4.1.27/Documentation/driver-model/ |
D | driver.txt | 74 Some may find the syntax of embedded struct initialization awkward or
|
/linux-4.1.27/arch/arm/crypto/ |
D | sha512-armv7-neon.S | 14 .syntax unified
|
D | sha1-armv7-neon.S | 14 .syntax unified
|
D | aesbs-core.S_shipped | 74 .syntax unified @ ARMv7-capable assembler is expected to handle this
|
D | sha256-core.S_shipped | 50 .syntax unified
|
/linux-4.1.27/Documentation/filesystems/cifs/ |
D | README | 65 "net" may also be helpful since it may someday provide easier mount syntax for 192 (cifs.o), you can use mount syntax like the following to access Samba or Windows 217 syntax) instead of the more widely used UNC format (i.e. \\server\share): 221 mechanisms, instead of specifying it after -o using the normal "pass=" syntax
|
/linux-4.1.27/drivers/media/usb/pwc/ |
D | philips.txt | 153 This somewhat cryptic syntax is best explained by a few examples:
|
/linux-4.1.27/arch/tile/ |
D | Kconfig | 1 # For a description of the syntax of this configuration file,
|
/linux-4.1.27/scripts/ |
D | spelling.txt | 941 synax||syntax
|
/linux-4.1.27/drivers/md/ |
D | Kconfig | 380 # nasty syntax but means make DM_MULTIPATH independent
|
/linux-4.1.27/Documentation/m68k/ |
D | kernel-options.txt | 15 kernel understands, or how the exact syntax for the ... option is, or 65 The first syntax gives the device by name. These names are converted
|
/linux-4.1.27/Documentation/cgroups/ |
D | cpusets.txt | 784 This is the syntax to use when writing in the cpus or mems files 805 The syntax is very simple:
|
/linux-4.1.27/drivers/char/ |
D | Kconfig | 114 how to pass options to the kernel at boot time.) The syntax of the
|
/linux-4.1.27/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 775 use of this syntax is to reattach the main console to stdin and stdout 1743 line or with uml_mconsole with the following syntax: 2364 device to add, with the same syntax as the kernel command line.
|
/linux-4.1.27/arch/arm/ |
D | Kconfig | 1552 ARM-Thumb syntax is needed.
|
/linux-4.1.27/Documentation/devicetree/ |
D | booting-without-of.txt | 1092 The syntax of the dtc tool is
|