Re: [PATCH] fs/aio: fix comment typos

Jan Kara <[email protected]>
Newsgroups gmane.linux.kernel.aio.general,gmane.linux.file-systems,gmane.linux.kernel
Message-ID <odioi7synjmo7vlotx7e2svjacqayrbokqws76bsxxkscntigo@px2xp3rfd55x>
On Fri 14-08-26 01:14:55, Mark Sercombe wrote:
> Fix two spelling mistakes in code comments. This is a comment only
> change with no functional impact.
> 
> Signed-off-by: Mark Sercombe <[email protected]>

Looks good. Feel free to add:

Reviewed-by: Jan Kara <[email protected]>

								Honza

> ---
>  fs/aio.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/aio.c b/fs/aio.c
> index f57fa21a2503..fb991c66afdb 100644
> --- a/fs/aio.c
> +++ b/fs/aio.c
> @@ -936,7 +936,7 @@ static int kill_ioctx(struct mm_struct *mm, struct kioctx *ctx,
>  
>  /*
>   * exit_aio: called when the last user of mm goes away.  At this point, there is
> - * no way for any new requests to be submited or any of the io_* syscalls to be
> + * no way for any new requests to be submitted or any of the io_* syscalls to be
>   * called on the context.
>   *
>   * There may be outstanding kiocbs, but free_ioctx() will explicitly wait on
> @@ -1280,7 +1280,7 @@ static long aio_read_events_ring(struct kioctx *ctx,
>  	 * The mutex can block and wake us up and that will cause
>  	 * wait_event_interruptible_hrtimeout() to schedule without sleeping
>  	 * and repeat. This should be rare enough that it doesn't cause
> -	 * peformance issues. See the comment in read_events() for more detail.
> +	 * performance issues. See the comment in read_events() for more detail.
>  	 */
>  	sched_annotate_sleep();
>  	mutex_lock(&ctx->ring_lock);
> -- 
> 2.55.0
> 
-- 
Jan Kara <[email protected]>
SUSE Labs, CR

--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to [email protected].  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"[email protected]">[email protected]</a>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.