| /linux-4.1.27/drivers/staging/gdm72xx/ |
| D | TODO | 2 - Clean up coding style to meet kernel standard.
|
| /linux-4.1.27/drivers/staging/rts5208/ |
| D | TODO | 2 - use kernel coding style
|
| /linux-4.1.27/drivers/usb/gadget/function/ |
| D | u_serial.c | 1027 gs_port_alloc(unsigned port_num, struct usb_cdc_line_coding *coding) in gs_port_alloc() argument
1055 port->port_line_coding = *coding; in gs_port_alloc()
1103 struct usb_cdc_line_coding coding; in gserial_alloc_line() local
1108 coding.dwDTERate = cpu_to_le32(9600); in gserial_alloc_line()
1109 coding.bCharFormat = 8; in gserial_alloc_line()
1110 coding.bParityType = USB_CDC_NO_PARITY; in gserial_alloc_line()
1111 coding.bDataBits = USB_CDC_1_STOP_BITS; in gserial_alloc_line()
1114 ret = gs_port_alloc(port_num, &coding); in gserial_alloc_line()
|
| /linux-4.1.27/drivers/staging/octeon-usb/ |
| D | TODO | 5 - kernel coding style
|
| /linux-4.1.27/drivers/staging/ft1000/ |
| D | TODO | 3 - coding style
|
| /linux-4.1.27/drivers/staging/mt29f_spinand/ |
| D | TODO | 5 - Clean up coding style to meet kernel standard.
|
| /linux-4.1.27/drivers/staging/sm7xxfb/ |
| D | TODO | 4 - use kernel coding style
|
| /linux-4.1.27/net/batman-adv/ |
| D | Kconfig | 44 This option enables network coding, a mechanism that aims to
49 network coding work.
|
| D | Makefile | 32 batman-adv-$(CONFIG_BATMAN_ADV_NC) += network-coding.o
|
| /linux-4.1.27/drivers/staging/lustre/ |
| D | TODO | 1 * Possible remaining coding style fix.
|
| /linux-4.1.27/drivers/staging/vt6656/ |
| D | TODO | 13 - use kernel coding style
|
| /linux-4.1.27/drivers/staging/vt6655/ |
| D | TODO | 15 - use kernel coding style
|
| /linux-4.1.27/drivers/staging/sm750fb/ |
| D | TODO | 3 - use kernel coding style
|
| /linux-4.1.27/drivers/staging/gdm724x/ |
| D | TODO | 2 - Clean up coding style to meet kernel standard. (80 line limit, netdev_err)
|
| /linux-4.1.27/arch/parisc/math-emu/ |
| D | README | 3 Linux coding style, please leave them in their funny format just in case
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | lifeview.txt | 1 collecting data about the lifeview models and the config coding on
|
| /linux-4.1.27/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
|
| D | 3.Early-stage | 4 to jump right in and start coding. As with any significant project,
|
| D | 2.Process | 304 up to Linux kernel coding or quality standards, but people may want to use
458 minor coding style issues. Unfortunately, such patches create a level of
|
| D | 6.Followthrough | 31 Many of the changes you may be asked to make - from coding style tweaks
|
| D | 1.Intro | 33 Section 4 is about the coding process; several pitfalls which have been
|
| D | 5.Posting | 40 - Make sure your code is compliant with the kernel coding style
|
| /linux-4.1.27/drivers/net/wan/ |
| D | farsync.h | 124 unsigned char coding; /* hdb3 b8zs */ member
|
| D | farsync.c | 234 u8 coding; member
1708 FST_WRB(card, suConfig.coding, info->coding); in set_conf_from_info()
1732 printk("Coding = %d\n", info->coding); in set_conf_from_info()
1822 info->coding = FST_RDB(card, suConfig.coding); in gather_conf_info()
|
| /linux-4.1.27/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-4.1.27/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,
65 Don't put multiple assignments on a single line either. Kernel coding style
536 This will make emacs go better with the kernel coding style for C
811 you should use, rather than explicitly coding some variant of them yourself.
|
| D | IRQ-domain.txt | 32 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
|
| D | HOWTO | 48 high standards for coding, style and procedure. These standards have
96 This describes the Linux kernel coding style, and some of the
|
| D | ManagementStyle | 10 simple coding style rules, so this document may or may not have anything
|
| D | memory-barriers.txt | 207 open-coding smp_read_barrier_depends().
|
| /linux-4.1.27/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-4.1.27/arch/arm/nwfpe/ |
| D | ChangeLog | 2 * Reformat all but softfloat files to get a consistent coding style.
|
| /linux-4.1.27/Documentation/block/ |
| D | biovecs.txt | 58 coding bvec iterators before, and having common implementation considerably
|
| /linux-4.1.27/fs/reiserfs/ |
| D | README | 94 Yura helps with benchmarking, coding hashes, and block pre-allocation
|
| /linux-4.1.27/arch/arm/kernel/ |
| D | entry-armv.S | 511 * coding round the lack of ldrht on older arches is pointless. Temporarily
|
| /linux-4.1.27/Documentation/networking/ |
| D | netdev-FAQ.txt | 171 Q: Someone said that the comment style and coding convention is different
|
| D | can.txt | 1205 Thomas Gleixner (LKML reviews, coding style, posting hints)
1216 Sam Ravnborg (reviews, coding style, kbuild help)
|
| D | arcnet.txt | 57 particular a lot of input and coding from Tomasz Motylewski. Starting with
|
| /linux-4.1.27/drivers/leds/ |
| D | Kconfig | 402 coding protocol to set the brightness.
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | usage-model.txt | 241 instead of hard coding static devices for each platform, the list of
|
| /linux-4.1.27/Documentation/scsi/ |
| D | tmscsim.txt | 423 Thanks to Doug Ledford, Gérard Roudier for support with SCSI coding.
|
| D | scsi_mid_low_api.txt | 338 First, Linus Torvalds's thoughts on C coding style can be found in the
356 and Adaptec have their own coding conventions.
|
| D | ChangeLog.lpfc | 269 lpfc_work_evt to comply with linux_scsi review coding style.
1010 * Some cosmetic coding style cleanups to lpfc_fcp.c.
|
| /linux-4.1.27/Documentation/mtd/ |
| D | nand_ecc.txt | 24 not use the right terminology, my coding theory class was almost 30
|
| /linux-4.1.27/Documentation/RCU/ |
| D | whatisRCU.txt | 244 Common coding practice uses rcu_dereference() to copy an
|
| /linux-4.1.27/Documentation/s390/ |
| D | Debugging390.txt | 188 vector table. This is a good thing & does simplify some of the kernel coding
|