Searched refs:silly (Results 1 – 12 of 12) sorted by relevance
/linux-3.4.99/drivers/mtd/ |
D | inftlcore.c | 214 int silly = inftl->nb_blocks; in INFTL_findfreeblock() local 239 if (!silly--) { in INFTL_findfreeblock() 255 int block, silly; in INFTL_foldchain() local 278 silly = MAX_LOOPS; in INFTL_foldchain() 310 if (!silly--) { in INFTL_foldchain() 483 int silly, silly2 = 3; in INFTL_findwriteunit() local 495 silly = MAX_LOOPS; in INFTL_findwriteunit() 523 if (!silly--) { in INFTL_findwriteunit() 644 int block, silly; in INFTL_trydeletechain() local 665 silly = MAX_LOOPS; in INFTL_trydeletechain() [all …]
|
D | nftlcore.c | 210 int silly = nftl->nb_blocks; in NFTL_findfreeblock() local 233 if (!silly--) { in NFTL_findfreeblock() 252 int silly; in NFTL_foldchain() local 272 silly = MAX_LOOPS; in NFTL_foldchain() 329 if (!silly--) { in NFTL_foldchain() 543 int silly, silly2 = 3; in NFTL_findwriteunit() local 556 silly = MAX_LOOPS; in NFTL_findwriteunit() 585 if (!silly--) { in NFTL_findwriteunit() 723 int silly = MAX_LOOPS; in nftl_readblock() local 756 if (!silly--) { in nftl_readblock()
|
/linux-3.4.99/fs/nfs/ |
D | unlink.c | 476 char silly[slen+1]; in nfs_sillyrename() local 493 sprintf(silly, ".nfs%*.*Lx", in nfs_sillyrename() 502 char *suffix = silly + slen - countersize; in nfs_sillyrename() 509 dentry->d_name.name, silly); in nfs_sillyrename() 511 sdentry = lookup_one_len(silly, dentry->d_parent, slen); in nfs_sillyrename()
|
/linux-3.4.99/Documentation/filesystems/ |
D | inotify.txt | 218 can use epoll, but requiring both is a silly and extraneous requirement. 223 thousand times is silly. If we can implement user-space's preferences
|
D | coda.txt | 1050 fetching the data in Venus vproc_vfscalls. This seems silly. If a
|
/linux-3.4.99/Documentation/ |
D | oops-tracing.txt | 79 the tools you can just do a silly program:
|
D | ManagementStyle | 253 silly. It can thus help get through the personal mental block we all
|
/linux-3.4.99/fs/befs/ |
D | ChangeLog | 79 * Abbandoned silly checks for a NULL superblock pointer in debug.c. [WD]
|
/linux-3.4.99/Documentation/development-process/ |
D | 5.Posting | 242 - Are you sure your patch is free of silly mistakes? You should always
|
/linux-3.4.99/Documentation/scsi/ |
D | ChangeLog.ncr53c8xx | 466 This has been called 'silly scheduler'.
|
/linux-3.4.99/ |
D | MAINTAINERS | 29 changes sent back with seemingly silly requests about formatting 30 and variable names. These aren't as silly as they seem. One
|
/linux-3.4.99/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 774 display output on an xterm. That's a silly example - the most common
|