Searched refs:sloppy (Results 1 – 17 of 17) sorted by relevance
2 hardware, or when using a sloppy port on some board, is memory errors.
91 int errors = 0, sloppy = 0; in parse_options() local185 else NTFS_GETOPT_WITH_DEFAULT("sloppy", sloppy, true) in parse_options()244 if (errors && !sloppy) in parse_options()246 if (sloppy) in parse_options()
449 return ctx->sloppy ? 1 : opt; in nfs_fs_context_parse_param()777 ctx->sloppy = true; in nfs_fs_context_parse_param()
98 bool sloppy; member
148 sloppy=<BOOL> If sloppy is specified, ignore unknown mount options.
17 subtract, we just xor. Thus, we tend to get a bit sloppy about
1398 bool sloppy = false; in cifs_parse_mount_options() local1726 sloppy = true; in cifs_parse_mount_options()2221 if (!sloppy && invalid) { in cifs_parse_mount_options()
1--- libmad-0.15.1b.orig/debian/changelog 2++ ...
1074 // This allows us to be a little bit sloppy in constructing
1433 case. Getting sloppy in this way is not a swift move because if a type
1981 with a symbol definition. Unix linkers allow this somewhat sloppy
2736 need _not_ be negative. In other words, sloppy code like
47971 the blit to determine whether we can be sloppy enough to allow memcpy.64341 sloppy focus or no window manager present was broken due to this89811 the blit to determine whether we can be sloppy enough to allow memcpy.156193 Xi: fix up sloppy class copying causing segfaults.