From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, mkchauras@gmail.com,
Nikhil Kumar Singh <nikhilks@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, mpe@ellerman.id.au,
npiggin@gmail.com, chleroy@kernel.org, adityag@linux.ibm.com,
mahesh@linux.ibm.com
Subject: Re: [PATCH v2] powerpc/64s: Clarify copy_and_flush() cache sync loop comment
Date: Thu, 6 Aug 2026 09:46:27 +0530 [thread overview]
Message-ID: <178598971879.942627.13294708865954950446.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260706082708.43918-1-nikhilks@linux.ibm.com>
On Mon, 06 Jul 2026 13:57:08 +0530, Nikhil Kumar Singh wrote:
> The value loaded into r0 in copy_and_flush() represents the number of
> 8-byte words processed between cache synchronization operations.
>
> The existing comment refers to cache line size, which can make it appear
> that the value is a cache line size in bytes rather than a loop count.
> Clarify the comment to explain that the loop processes 8 words (64 bytes)
> per cache synchronization iteration, and that increasing the value would
> skip cache maintenance for intermediate cache lines.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/64s: Clarify copy_and_flush() cache sync loop comment
https://git.kernel.org/powerpc/c/76ea1257924f64521f708db91c99014ce7249bbf
cheers
next prev parent reply other threads:[~2026-08-06 4:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 18:27 [PATCH] " Nikhil Kumar Singh
2026-07-01 18:38 ` Aditya Gupta
2026-07-02 5:28 ` Mukesh Kumar Chaurasiya
2026-07-06 8:27 ` [PATCH v2] " Nikhil Kumar Singh
2026-07-07 5:38 ` Mukesh Kumar Chaurasiya
2026-07-07 7:18 ` Nikhil Kumar Singh
2026-07-07 7:24 ` Mukesh Kumar Chaurasiya
2026-07-09 6:10 ` Nikhil Kumar Singh
2026-07-09 8:32 ` Mukesh Kumar Chaurasiya
2026-07-17 11:55 ` Amit Machhiwal
2026-07-17 6:40 ` Aditya Gupta
2026-07-17 14:52 ` Mahesh J Salgaonkar
2026-08-06 4:16 ` Madhavan Srinivasan [this message]
2026-07-14 10:30 ` [PATCH] " Mahesh J Salgaonkar
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=178598971879.942627.13294708865954950446.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mkchauras@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=nikhilks@linux.ibm.com \
--cc=npiggin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®