| /linux-3.4.99/drivers/usb/gadget/ |
| D | u_serial.c | 1029 gs_port_alloc(unsigned port_num, struct usb_cdc_line_coding *coding) in gs_port_alloc() argument
1048 port->port_line_coding = *coding; in gs_port_alloc()
1077 struct usb_cdc_line_coding coding; in gserial_setup() local
1105 coding.dwDTERate = cpu_to_le32(9600); in gserial_setup()
1106 coding.bCharFormat = 8; in gserial_setup()
1107 coding.bParityType = USB_CDC_NO_PARITY; in gserial_setup()
1108 coding.bDataBits = USB_CDC_1_STOP_BITS; in gserial_setup()
1115 status = gs_port_alloc(i, &coding); in gserial_setup()
|
| /linux-3.4.99/drivers/staging/ft1000/ |
| D | TODO | 3 - coding style
|
| /linux-3.4.99/drivers/staging/sm7xx/ |
| D | TODO | 4 - use kernel coding style
|
| /linux-3.4.99/drivers/staging/rtl8187se/ |
| D | TODO | 8 - use kernel coding style
|
| /linux-3.4.99/drivers/staging/vt6656/ |
| D | TODO | 13 - use kernel coding style
|
| /linux-3.4.99/drivers/staging/rts5139/ |
| D | TODO | 3 - use kernel coding style
|
| /linux-3.4.99/drivers/staging/rts_pstor/ |
| D | TODO | 3 - use kernel coding style
|
| /linux-3.4.99/drivers/staging/vt6655/ |
| D | TODO | 15 - use kernel coding style
|
| /linux-3.4.99/arch/parisc/math-emu/ |
| D | README | 3 Linux coding style, please leave them in their funny format just in case
|
| /linux-3.4.99/drivers/staging/tidspbridge/ |
| D | TODO | 13 * Use kernel coding style
|
| /linux-3.4.99/Documentation/video4linux/ |
| D | lifeview.txt | 1 collecting data about the lifeview models and the config coding on
|
| /linux-3.4.99/Documentation/development-process/ |
| D | 4.Coding | 9 This section will examine the coding process. We'll start with a look at a
19 The kernel has long had a standard coding style, described in
22 a substantial amount of code in the kernel which does not meet the coding
26 The first of these is to believe that the kernel coding standards do not
35 Occasionally, the kernel's coding style will run into conflict with an
42 urgently in need of coding style fixes. Developers may start to generate
45 pure coding style fixes are seen as noise by the development community;
48 on it for other reasons, but coding style changes should not be made for
51 The coding style document also should not be read as an absolute law which
294 variety of potential coding problems; it can also propose fixes for those
|
| D | 7.AdvancedTopics | 164 are mostly concerned with coding style and whether code lines have trailing
|
| /linux-3.4.99/drivers/net/wan/ |
| D | farsync.h | 124 unsigned char coding; /* hdb3 b8zs */ member
|
| D | farsync.c | 233 u8 coding; member
1717 FST_WRB(card, suConfig.coding, info->coding); in set_conf_from_info()
1741 printk("Coding = %d\n", info->coding); in set_conf_from_info()
1831 info->coding = FST_RDB(card, suConfig.coding); in gather_conf_info()
|
| /linux-3.4.99/drivers/staging/wlags49_h2/ |
| D | TODO | 21 - verify the code against the coding standards for a proper linux
|
| /linux-3.4.99/drivers/staging/wlags49_h25/ |
| D | TODO | 21 - verify the code against the coding standards for a proper linux
|
| /linux-3.4.99/Documentation/hwmon/ |
| D | submitting-patches | 19 such as "I don't like that coding style". Keep in mind that each unnecessary
20 warning helps hiding a real problem. If you don't like the kernel coding
|
| /linux-3.4.99/Documentation/ |
| D | digsig.txt | 18 coding style, and checkpatch.pl reported errors and warnings have been fixed.
|
| D | CodingStyle | 2 Linux kernel coding style
4 This is a short document describing the preferred coding style for the
10 First off, I'd suggest printing out a copy of the GNU coding standards,
66 Don't put multiple assignments on a single line either. Kernel coding style
504 This will make emacs go better with the kernel coding style for C
754 you should use, rather than explicitly coding some variant of them yourself.
|
| D | IRQ-domain.txt | 17 preferred over interrupt controller drivers open coding their own
|
| D | unaligned-memory-access.txt | 71 coding practice. After all, you don't have a great deal of control over
|
| /linux-3.4.99/Documentation/crypto/ |
| D | descore-readme.txt | 143 (i.e. the author didn't sit down and think before coding),
212 be able to get performance equal to assembly-coding, except that:
220 however, if you like assembly coding, the 386 does have 7 32-bit registers,
231 coding notes
|
| /linux-3.4.99/arch/arm/nwfpe/ |
| D | ChangeLog | 2 * Reformat all but softfloat files to get a consistent coding style.
|
| /linux-3.4.99/fs/reiserfs/ |
| D | README | 94 Yura helps with benchmarking, coding hashes, and block pre-allocation
|