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, 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: Thu, 27 Feb 2025 07:50:08 -0800 [thread overview]
Message-ID: <20250227155008.25388-1-sj@kernel.org> (raw)
In-Reply-To: <CAJGd785bhaXV4=R8dL-yNdQLN3YsJL+L+XQH3jwqYdYCCy5LNA@mail.gmail.com>
On Thu, 27 Feb 2025 07:35:00 -0800 bus710 <bus710@gmail.com> wrote:
> I was wondering how others live with the git send-email all the time,
> so I searched for alternatives.
> Then I found out that some people use terminal email clients like
> Mutt,
Yes, dealing with mails is not easy for beginners. I therefore introduced you
hkml before:
https://lore.kernel.org/20250225000925.1654-1-sj@kernel.org
If Mutt setup doesn't go well, and you haven't tried hkml yet, you could give
hkml a try, too.
> and learned that the inline patch is the right way, not
> attached.
> Let me do the inline patch if there are more chances in the future.
Yes, that should be the right approach.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-02-27 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 18:42 [PATCH] samples/damon: a typo in the kconfig - sameple 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 18:07 bus710
2025-02-24 19:01 ` SeongJae Park
2025-02-24 20:06 ` bus710
2025-02-24 21:35 ` SeongJae Park
2025-02-25 0:09 ` 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=20250227155008.25388-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bus710@gmail.com \
--cc=damon@lists.linux.dev \
--cc=kernel-team@meta.com \
--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 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.