From: Catalin Marinas <catalin.marinas@arm.com>
To: Yang Shi <yang@os.amperecomputing.com>
Cc: Dev Jain <dev.jain@arm.com>,
will@kernel.org, ryan.roberts@arm.com, rppt@kernel.org,
shijie@os.amperecomputing.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64/pageattr: Propagate return value from __change_memory_common
Date: Wed, 19 Nov 2025 18:06:23 +0000 [thread overview]
Message-ID: <aR4HH1WyCzQk8sqJ@arm.com> (raw)
In-Reply-To: <3aa3558d-cfc6-43a1-8c73-9b01ed1e2b3e@os.amperecomputing.com>
On Wed, Nov 12, 2025 at 02:27:49PM -0800, Yang Shi wrote:
> The fix looks good to me. Reviewed-by: Yang Shi
> <yang@os.amperecomputing.com>
BTW, I think tools like b4 which I use to apply patches will ignored the
reviewed-by tag as it's not on a separate line (I haven't checked the
latest b4 version but I've seen it happening in the past).
--
Catalin
next prev parent reply other threads:[~2025-11-19 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 6:27 [PATCH 0/2] arm64/mm: A fix and a documentation bit for change_memory_common() Dev Jain
2025-11-12 6:27 ` [PATCH 1/2] arm64/pageattr: Propagate return value from __change_memory_common Dev Jain
2025-11-12 22:27 ` Yang Shi
2025-11-19 18:06 ` Catalin Marinas [this message]
2025-11-19 19:33 ` Yang Shi
2025-11-13 11:55 ` Ryan Roberts
2025-11-13 17:38 ` Yang Shi
2025-11-24 15:11 ` Will Deacon
2025-11-24 18:09 ` Ryan Roberts
2025-11-24 19:10 ` Will Deacon
2025-11-19 18:03 ` Catalin Marinas
2025-11-20 4:10 ` Dev Jain
2025-11-12 6:27 ` [PATCH 2/2] arm64/mm: Document why linear map split failure upon vm_reset_perms is not problematic Dev Jain
2025-11-12 22:34 ` Yang Shi
2025-11-13 12:25 ` Ryan Roberts
2025-11-28 15:52 ` [PATCH 0/2] arm64/mm: A fix and a documentation bit for change_memory_common() Catalin Marinas
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=aR4HH1WyCzQk8sqJ@arm.com \
--to=catalin.marinas@arm.com \
--cc=dev.jain@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shijie@os.amperecomputing.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.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 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.