LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "email@example.com" <firstname.lastname@example.org> To: 'James Morse' <email@example.com> Cc: "'firstname.lastname@example.org'" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "firstname.lastname@example.org" <email@example.com> Subject: RE: About resctrl code rebase Date: Mon, 6 Sep 2021 06:19:07 +0000 [thread overview] Message-ID: <TYAPR01MB6330974317488E525DBA4E2E8BD29@TYAPR01MB6330.jpnprd01.prod.outlook.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi, James Morse Thanks for your reply. > On 01/09/2021 09:35, email@example.com wrote: > >> As you known, Fujitsu is implementing a feature that add A64FX's > >> cache control function into resctrl. > > >> Fujitsu will implement this feature base on your rebased code. I > >> think the commit of refactoring arch/x86 implementation of resctrl > >> has been merged into the x86/cache branch. > >> https://lore.kernel.org/lkml/162871088112.395.12879267279872673224.ti > >> p-bot2@tip-bot2/ > > I'm afraid this was only a small part of it. > > I've also posted the next series here: > https://firstname.lastname@example.org > / > > and there are a couple more after that. I understand. > >> I would like to know whether you have rebased these codes that move > >> the common parts of multiple architectures to somewhere. > >> And where is the rebase code? > >> In addition, when will you release the latest MPAM patch? > > I will keep posting 'the next part' of the x86 changes once the earlier part is > reviewed. > (please help!) I will check these patches. And I'm going to test these patches on machine with x86. Best regards, Tan Shaopeng > I can't push the latest branch until the ACPI spec is published, but I hope that > will happen this month. > > > > I'm afraid that my message may not have reached you. > > Yes, I'm horribly behind with email!
next prev parent reply other threads:[~2021-09-06 6:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-01 8:35 About resctrl code rebase tan.shaopeng 2021-09-01 17:04 ` James Morse 2021-09-06 6:19 ` tan.shaopeng [this message] 2021-11-24 11:17 ` tan.shaopeng
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=TYAPR01MB6330974317488E525DBA4E2E8BD29@TYAPR01MB6330.jpnprd01.prod.outlook.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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: linkBe 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; as well as URLs for NNTP newsgroup(s).