From: James Morse <james.morse@arm.com>
To: Zeng Heng <zengheng4@huawei.com>,
rohit.mathew@arm.com, amitsinght@marvell.com,
sdonthineni@nvidia.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, liwei391@huawei.com
Subject: Re: [PATCH mpam/v6.10-rc1 RFC 0/4] arm_mpam: Fix several minor issues
Date: Fri, 20 Dec 2024 17:51:21 +0000 [thread overview]
Message-ID: <ee78c9e9-ff47-416c-8bb2-55b0a903e13a@arm.com> (raw)
In-Reply-To: <20240722040140.515173-1-zengheng4@huawei.com>
Hello!
On 22/07/2024 05:01, Zeng Heng wrote:
> After completing the necessary software adaptation for the local chipset,
> the MPAM function is successfully enabled. After related tests are
> completed, some issues were discovered and here attempt to fix them.
>
> Hope to get some suggestions for modifications, if I miss any rules should
> be followed, please let me know.
Sorry for the delay following these up - they should all be fixed in the newer
versions of the tree. I've added 'CC' tags to the patches you fixed here.
Thanks,
James
next prev parent reply other threads:[~2024-12-20 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 4:01 Zeng Heng
2024-07-22 4:01 ` [PATCH mpam/v6.10-rc1 RFC 1/4] arm_mpam: Correct MBA granularity calculation Zeng Heng
2024-07-22 4:01 ` [PATCH mpam/v6.10-rc1 RFC 2/4] arm_mpam: Fix the range calculation of the implemented bits Zeng Heng
2024-07-22 4:01 ` [PATCH mpam/v6.10-rc1 RFC 3/4] arm_mpam: Correct the judgment condition of the CMAX feature Zeng Heng
2024-07-22 4:01 ` [PATCH mpam/v6.10-rc1 RFC 4/4] arm_mpam: Fix typo about mbw_min controls Zeng Heng
2024-12-20 17:51 ` James Morse [this message]
2025-01-04 10:28 ` [PATCH mpam/v6.10-rc1 RFC 0/4] arm_mpam: Fix several minor issues Zeng Heng
-- strict thread matches above, loose matches on Subject: below --
2024-07-22 4:01 Zeng Heng
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=ee78c9e9-ff47-416c-8bb2-55b0a903e13a@arm.com \
--to=james.morse@arm.com \
--cc=amitsinght@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=rohit.mathew@arm.com \
--cc=sdonthineni@nvidia.com \
--cc=zengheng4@huawei.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®