linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: Trivial typo fix in the file coredump.c
Date: Mon, 15 Mar 2021 22:23:12 -0700	[thread overview]
Message-ID: <515c0dca-2ce5-4c15-0682-b95374cb73e2@infradead.org> (raw)
In-Reply-To: <20210316050302.3816253-1-unixbhaskar@gmail.com>

On 3/15/21 10:03 PM, Bhaskar Chowdhury wrote:
> 
> s/postion/position/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  Al, I hope this time I read the comments well enough,if still
>  I am at fault , curse me!
> 
>  fs/coredump.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/coredump.c b/fs/coredump.c
> index 1c0fdc1aa70b..3ecae122ffd9 100644
> --- a/fs/coredump.c
> +++ b/fs/coredump.c
> @@ -923,7 +923,7 @@ EXPORT_SYMBOL(dump_align);
> 
>  /*
>   * Ensures that file size is big enough to contain the current file
> - * postion. This prevents gdb from complaining about a truncated file
> + * position. This prevents gdb from complaining about a truncated file
>   * if the last "write" to the file was dump_skip.
>   */
>  void dump_truncate(struct coredump_params *cprm)
> --


-- 
~Randy


      reply	other threads:[~2021-03-16  5:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  5:03 [PATCH] fs: Trivial typo fix in the file coredump.c Bhaskar Chowdhury
2021-03-16  5:23 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=515c0dca-2ce5-4c15-0682-b95374cb73e2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=unixbhaskar@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).