All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>,
	jaegeuk@kernel.org, mhiramat@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, quic_pkondeti@quicinc.com
Subject: Re: [PATCH 2/2] f2fs: fix the msg data type
Date: Sat, 29 Oct 2022 10:55:39 +0800	[thread overview]
Message-ID: <4de69c67-b18f-0b1e-6a55-642120e8c675@kernel.org> (raw)
In-Reply-To: <1666861961-12924-2-git-send-email-quic_mojha@quicinc.com>

On 2022/10/27 17:12, Mukesh Ojha wrote:
> Data type of msg in f2fs_write_checkpoint trace should
> be const char * instead of char *.
> 
> Signed-off-by: Mukesh Ojha <quic_mojha@quicinc.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>,
	jaegeuk@kernel.org, mhiramat@kernel.org
Cc: quic_pkondeti@quicinc.com, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: fix the msg data type
Date: Sat, 29 Oct 2022 10:55:39 +0800	[thread overview]
Message-ID: <4de69c67-b18f-0b1e-6a55-642120e8c675@kernel.org> (raw)
In-Reply-To: <1666861961-12924-2-git-send-email-quic_mojha@quicinc.com>

On 2022/10/27 17:12, Mukesh Ojha wrote:
> Data type of msg in f2fs_write_checkpoint trace should
> be const char * instead of char *.
> 
> Signed-off-by: Mukesh Ojha <quic_mojha@quicinc.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2022-10-29  2:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  9:12 [PATCH v2 1/2] f2fs: fix the assign logic of iocb Mukesh Ojha
2022-10-27  9:12 ` [f2fs-dev] " Mukesh Ojha
2022-10-27  9:12 ` [PATCH 2/2] f2fs: fix the msg data type Mukesh Ojha
2022-10-27  9:12   ` [f2fs-dev] " Mukesh Ojha
2022-10-27 10:17   ` Pavan Kondeti
2022-10-27 10:17     ` [f2fs-dev] " Pavan Kondeti
2022-10-27 10:30     ` Pavan Kondeti
2022-10-27 10:30       ` Pavan Kondeti
2022-10-29  2:55   ` Chao Yu [this message]
2022-10-29  2:55     ` [f2fs-dev] " Chao Yu
2022-10-29  2:55 ` [f2fs-dev] [PATCH v2 1/2] f2fs: fix the assign logic of iocb Chao Yu
2022-10-29  2:55   ` Chao Yu

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=4de69c67-b18f-0b1e-6a55-642120e8c675@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=quic_mojha@quicinc.com \
    --cc=quic_pkondeti@quicinc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.