Searched refs:irrelevant (Results 1 – 16 of 16) sorted by relevance
| /linux-3.4.99/net/ |
| D | nonet.c | 17 static int sock_no_open(struct inode *irrelevant, struct file *dontcare) in sock_no_open() argument
|
| D | socket.c | 108 static int sock_no_open(struct inode *irrelevant, struct file *dontcare);
493 static int sock_no_open(struct inode *irrelevant, struct file *dontcare) in sock_no_open() argument
|
| /linux-3.4.99/Documentation/scsi/ |
| D | aha152x.txt | 119 irrelevant anyway).
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | romfs.txt | 156 to romfs-subscribe@shadow.banki.hu, the content is irrelevant.
|
| D | coda.txt | 1341 iinn irrelevant
1345 irrelevant
1362 iinn irrelevant
1365 irrelevant
|
| D | ntfs.txt | 211 Note this option is irrelevant for read-only mounts.
|
| /linux-3.4.99/Documentation/vm/ |
| D | transhuge.txt | 16 factors. The first factor is almost completely irrelevant and it's not
|
| /linux-3.4.99/Documentation/development-process/ |
| D | 5.Posting | 185 You should avoid including changes to irrelevant files (those generated by
|
| D | 4.Coding | 137 irrelevant.
|
| /linux-3.4.99/Documentation/devicetree/ |
| D | usage-model.txt | 105 In the majority of cases, the machine identity is irrelevant, and the
|
| D | booting-without-of.txt | 791 irrelevant here). Additionally, node and property names should always
|
| /linux-3.4.99/Documentation/isdn/ |
| D | README | 26 Subject irrelevant, in the message body:
|
| /linux-3.4.99/scripts/genksyms/ |
| D | parse.tab.c_shipped | 1803 is really irrelevant to the linkage. */
|
| /linux-3.4.99/arch/ia64/kernel/ |
| D | perfmon.c | 2158 pfm_no_open(struct inode *irrelevant, struct file *dontcare) in pfm_no_open() argument
|
| /linux-3.4.99/Documentation/block/ |
| D | biodoc.txt | 402 avoid cache related fields which are irrelevant in the direct/page i/o path,
|
| /linux-3.4.99/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 625 command line is irrelevant.
|