Fix some spelling mistakes, and modify the order of the parameter comments to be consistent with the order of the parameters passed to the function.
Showing the changes to kernel (1 of 1 file). Show all
Unified · Split
| @@ -338,8 +338,8 @@ static void helper_unlock(void) · 337 unmodified lines | ||
| 338 | 338 | * @argv: arg vector for process |
| 339 | 339 | * @envp: environment for process |
| 340 | 340 | * @gfp_mask: gfp mask for memory allocation |
| 341 | − * @cleanup: a cleanup function | |
| 342 | 341 | * @init: an init function |
| 342 | + * @cleanup: a cleanup function | |
| 343 | 343 | * @data: arbitrary context sensitive data |
| 344 | 344 | * |
| 345 | 345 | * Returns either %NULL on allocation failure, or a subprocess_info |
| @@ -350,7 +350,7 @@ static void helper_unlock(void) · 4 unmodified lines | ||
| 350 | 350 | * exec. A non-zero return code causes the process to error out, exit, |
| 351 | 351 | * and return the failure to the calling process |
| 352 | 352 | * |
| 353 | − * The cleanup function is just before ethe subprocess_info is about to | |
| 353 | + * The cleanup function is just before the subprocess_info is about to | |
| 354 | 354 | * be freed. This can be used for freeing the argv and envp. The |
| 355 | 355 | * Function must be runnable in either a process context or the |
| 356 | 356 | * context in which call_usermodehelper_exec is called. |
| @@ -386,7 +386,7 @@ EXPORT_SYMBOL(call_usermodehelper_setup); · 29 unmodified lines | ||
| 386 | 386 | |
| 387 | 387 | /** |
| 388 | 388 | * call_usermodehelper_exec - start a usermode application |
| 389 | − * @sub_info: information about the subprocessa | |
| 389 | + * @sub_info: information about the subprocess | |
| 390 | 390 | * @wait: wait for the application to finish and return status. |
| 391 | 391 | * when UMH_NO_WAIT don't wait at all, but you get no useful error back |
| 392 | 392 | * when the program couldn't be exec'ed. This makes it safe to call |