linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Yi Wang <wang.yi59@zte.com.cn>
Cc: jeffm@suse.com, jack@suse.cz, reiserfs-devel@vger.kernel.org,
	linux-kernel@vger.kernel.org, xue.zhihong@zte.com.cn,
	wang.liang82@zte.com.cn, Liao Pingfang <liao.pingfang@zte.com.cn>
Subject: Re: [PATCH] reiserfs: Replace kmalloc with kcalloc in the comment
Date: Fri, 29 May 2020 08:52:58 +0200	[thread overview]
Message-ID: <20200529065258.GK14550@quack2.suse.cz> (raw)
In-Reply-To: <1590714150-15895-1-git-send-email-wang.yi59@zte.com.cn>

On Fri 29-05-20 09:02:30, Yi Wang wrote:
> From: Liao Pingfang <liao.pingfang@zte.com.cn>
> 
> Use kcalloc instead of kmalloc in the comment according to
> the previous kcalloc() call.
> 
> Signed-off-by: Liao Pingfang <liao.pingfang@zte.com.cn>

Thanks. I've added the patch to my tree.

								Honza

> ---
>  fs/reiserfs/inode.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/reiserfs/inode.c b/fs/reiserfs/inode.c
> index 6419e6d..21ad762 100644
> --- a/fs/reiserfs/inode.c
> +++ b/fs/reiserfs/inode.c
> @@ -1066,7 +1066,7 @@ int reiserfs_get_block(struct inode *inode, sector_t block,
>  			} else {
>  				/* paste hole to the indirect item */
>  				/*
> -				 * If kmalloc failed, max_to_insert becomes
> +				 * If kcalloc failed, max_to_insert becomes
>  				 * zero and it means we only have space for
>  				 * one block
>  				 */
> -- 
> 2.9.5
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2020-05-29  6:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  1:02 [PATCH] reiserfs: Replace kmalloc with kcalloc in the comment Yi Wang
2020-05-29  6:52 ` Jan Kara [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=20200529065258.GK14550@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=jeffm@suse.com \
    --cc=liao.pingfang@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=wang.liang82@zte.com.cn \
    --cc=wang.yi59@zte.com.cn \
    --cc=xue.zhihong@zte.com.cn \
    /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).