Searched refs:dash (Results 1 – 9 of 9) sorted by relevance
155 char *dash; in fault_opcodes_write() local167 dash = strchr(token, '-'); in fault_opcodes_write()168 if (dash) in fault_opcodes_write()169 *dash = '\0'; in fault_opcodes_write()172 if (dash) { in fault_opcodes_write()173 token = dash + 1; in fault_opcodes_write()
232 char *dash; in mc13783_adc_probe() local240 dash = strchr(priv->name, '-'); in mc13783_adc_probe()241 if (dash) in mc13783_adc_probe()242 *dash = '\0'; in mc13783_adc_probe()
154 char *dash, *end_ptr; in build_memory_map() local160 dash = strstr(line, "-"); in build_memory_map()161 dash[0] = 0x20; in build_memory_map()
38 * The test cases should run on dash (busybox shell) for testing on
36 a dash: ``cx18-0``, ``cx18-1``, etc. This function returns the instance number.
544 valid letters (rwxatbRWXATB) and the dash ('-') character are allowed in545 access specifications. The dash is a placeholder, so "a-r" is the same546 as "ar". A lone dash is used to specify that no access should be allowed.
245 the ``M`` specifier to use dash (-) separators instead of the default
205 stable that does *not* belong in the commit log, then use the three dash
214 * In syslog.conf, you can prefix entries with a dash `-` to omit syncing the
