linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: bus710 <bus710@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	damon@lists.linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples/damon: a typo in the kconfig - sameple
Date: Mon, 24 Feb 2025 11:01:45 -0800	[thread overview]
Message-ID: <20250224190145.24272-1-sj@kernel.org> (raw)
In-Reply-To: <20250224180709.2167187-1-bus710@gmail.com>

Hi bus710,

On Mon, 24 Feb 2025 10:07:09 -0800 bus710 <bus710@gmail.com> wrote:

> Signed-off-by: bus710 <bus710@gmail.com>

Reviewed-by: SeongJae Park <sj@kernel.org>

Thank you for this fix!

> ---
> Hi SeongJae Park, 
> 
> I found a trivial typo in the Kconfig file of the damon sample module
> while I was trying to do some experiments with sample codes.
> The word "sameple" should be "sample", I believe. Please find the diff below.

I think the above sentence is better to be added to the "Explanation Body"[1]
part of this patch.  This shouldn't be a blocker of this patch though, since it
is very simple.  Please consider doing so if you have a chance to send another
patch in future, though.

> 
> Since the title should follow the format of the project, I sent a new
> email to the mailing list. Sorry for the inconvenience.
> 
> Thanks for the interesting project! DAMON will be very useful for many
> projects.
> 
> Thanks,
> 
> Ps: I found I didn't change the subject! Sorry this is my very first
> communication with the project.

No worry, everyone makes mistakes, like I made the typo! ;)  Thank you for
finding and fixing mine!

[1] https://docs.kernel.org/process/submitting-patches.html#explanation-body


Thanks,
SJ

> 
> 
>  samples/damon/Kconfig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/samples/damon/Kconfig b/samples/damon/Kconfig
> index 63f6dcd71daa..564c49ed69a2 100644
> --- a/samples/damon/Kconfig
> +++ b/samples/damon/Kconfig
> @@ -3,7 +3,7 @@
>  menu "DAMON Samples"
>  
>  config SAMPLE_DAMON_WSSE
> -	bool "DAMON sameple module for working set size estimation"
> +	bool "DAMON sample module for working set size estimation"
>  	depends on DAMON && DAMON_VADDR
>  	help
>  	  This builds DAMON sample module for working set size estimation.
> @@ -15,7 +15,7 @@ config SAMPLE_DAMON_WSSE
>  	  If unsure, say N.
>  
>  config SAMPLE_DAMON_PRCL
> -	bool "DAMON sameple module for access-aware proactive reclamation"
> +	bool "DAMON sample module for access-aware proactive reclamation"
>  	depends on DAMON && DAMON_VADDR
>  	help
>  	  This builds DAMON sample module for access-aware proactive
> -- 
> 2.47.2


       reply	other threads:[~2025-02-24 19:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250224180709.2167187-1-bus710@gmail.com>
2025-02-24 19:01 ` SeongJae Park [this message]
2025-02-26 18:42 SeongJae Park
2025-02-26 19:05 ` SeongJae Park
2025-02-26 21:37 ` Andrew Morton
2025-02-26 22:56   ` SeongJae Park
2025-02-26 23:07     ` bus710
2025-02-27  7:03       ` bus710
2025-02-27 15:35         ` bus710
2025-02-27 15:50           ` SeongJae Park

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=20250224190145.24272-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bus710@gmail.com \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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