From: Yun Levi <ppbuk5246@gmail.com>
To: SeongJae Park <sj@kernel.org>
Cc: akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] damon: Use pmdp_get instead of drectly dereferencing pmd.
Date: Fri, 28 Jul 2023 07:58:56 +0100 [thread overview]
Message-ID: <CAM7-yPQEnppWQ4j7mc4WG3POKbjzOLynkFXsSw47GRhSUaTawg@mail.gmail.com> (raw)
In-Reply-To: <20230727215318.43455-1-sj@kernel.org>
On Thu, Jul 27, 2023 at 10:53 PM SeongJae Park <sj@kernel.org> wrote:
>
> Hi Levi,
>
>
> Thank you for quick respin.
>
> I still hope the subject to drop the ending period, and start the subject with
> lowercase, like other mm/damon/ commits.
>
Sorry to bother you, I should find why the ending period inserted..
> > As ptep_get, Use the pmdp_get wrapper when we accessing pmdval
> > instead of directly dereferencing pmd.
>
> Based on the usual git commit message line length recommendation (72
> characters), there is nothing really wrong, but putting 'instead' at the first
> line may look more consistent with other messages.
> Since this is the good place to put additional comments not suitable for the
> changelog[2], it would be helpful if you could put changes of this patch that
> made after the v1 here, from next time.
>
> Above comments are only my trivial and personal preferences, so I wouldn't ask
> you to respin, unless you really want to.
>
> [1] https://github.com/torvalds/linux/pull/17
> [2] https://docs.kernel.org/process/submitting-patches.html#the-canonical-patch-format
Thanks for letting me know some details why I missed :)
Many thanks.
--------
Sincerely,
Levi.
prev parent reply other threads:[~2023-07-28 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 21:21 Levi Yun
2023-07-27 21:53 ` SeongJae Park
2023-07-28 6:58 ` Yun Levi [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=CAM7-yPQEnppWQ4j7mc4WG3POKbjzOLynkFXsSw47GRhSUaTawg@mail.gmail.com \
--to=ppbuk5246@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--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