Searched refs:silly (Results 1 – 17 of 17) sorted by relevance
| /Linux-v4.19/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-v4.19/fs/nfs/ |
| D | unlink.c | 448 unsigned char silly[SILLYNAME_LEN + 1]; in nfs_sillyrename() local
472 slen = scnprintf(silly, sizeof(silly), in nfs_sillyrename()
478 dentry, silly); in nfs_sillyrename()
480 sdentry = lookup_one_len(silly, dentry->d_parent, slen); in nfs_sillyrename()
|
| /Linux-v4.19/scripts/kconfig/tests/ |
| D | pytest.ini | 5 # them as top-level modules. It is silly to prefix or suffix a test file with
|
| /Linux-v4.19/fs/orangefs/ |
| D | orangefs-debugfs.c | 434 size_t silly = 0; in orangefs_debug_write() local
452 silly = count; in orangefs_debug_write()
535 if (silly) in orangefs_debug_write()
536 rc = silly; in orangefs_debug_write()
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | inotify.txt | 27 can use epoll, but requiring both is a silly and extraneous requirement.
32 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-v4.19/Documentation/core-api/ |
| D | boot-time-mm.rst | 86 documented it would be silly to omit them. Besides, reading the
|
| /Linux-v4.19/Documentation/fmc/ |
| D | fmc-chardev.txt | 9 the name can be a silly fmc-0000 look-alike if the device has no
|
| /Linux-v4.19/Documentation/block/ |
| D | biovecs.txt | 109 over all the biovecs in the new bio - which is silly as it's not needed.
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | imx28-tx28.dts | 171 * a silly way to create a 1:1 relationship between the
|
| /Linux-v4.19/fs/befs/ |
| D | ChangeLog | 79 * Abbandoned silly checks for a NULL superblock pointer in debug.c. [WD]
|
| /Linux-v4.19/Documentation/process/ |
| D | management-style.rst | 265 silly. It can thus help get through the personal mental block we all
|
| D | 5.Posting.rst | 259 - Are you sure your patch is free of silly mistakes? You should always
|
| /Linux-v4.19/Documentation/scsi/ |
| D | ChangeLog.ncr53c8xx | 466 This has been called 'silly scheduler'.
|
| /Linux-v4.19/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 774 display output on an xterm. That's a silly example - the most common
|
| /Linux-v4.19/ |
| 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
|
