From: bus710 <bus710@gmail.com>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, kernel-team@meta.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] samples/damon: a typo in the kconfig - sameple
Date: Wed, 26 Feb 2025 15:07:18 -0800 [thread overview]
Message-ID: <CAJGd785Eu7iuVwYnewaUm38NJcKzB-xkZwdRiYR9Yo9Qwaoffg@mail.gmail.com> (raw)
In-Reply-To: <20250226225605.2000-1-sj@kernel.org>
On Wed, Feb 26, 2025 at 2:56 PM SeongJae Park <sj@kernel.org> wrote:
>
> On Wed, 26 Feb 2025 13:37:03 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Wed, 26 Feb 2025 10:42:04 -0800 SeongJae Park <sj@kernel.org> wrote:
> >
> > > From: bus710 <bus710@gmail.com>
> >
> > Full names are preferred, please. Actually I think it's "required".
>
> Thank you for letting me clearly know this. I'll request full names to DAMON
> patch authors from next time.
>
> bus710, we could still update the patch before it is merged into the mainline.
> If you could, please let us know your full name and if we can update the patch
> with that.
>
> >
> > I'll apply it anyway due to the patch's minor nature, thanks.
>
> I agree this is a simple enough patch that the name doesn't really matter.
> Thank you Andrew :)
>
>
> Thanks,
> SJ
Oh, yes. I was a little worried if I added too much noise for such a
small work, but I shouldn't miss this opportunity to leave my name in
Linux history.
Let me prepare a new patch as soon as possible.
next prev parent reply other threads:[~2025-02-26 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2025-02-27 7:03 ` bus710
2025-02-27 15:35 ` bus710
2025-02-27 15:50 ` SeongJae Park
[not found] <20250224180709.2167187-1-bus710@gmail.com>
2025-02-24 19:01 ` 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=CAJGd785Eu7iuVwYnewaUm38NJcKzB-xkZwdRiYR9Yo9Qwaoffg@mail.gmail.com \
--to=bus710@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.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