From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, mikuback@linux.microsoft.com
Cc: "Ni, Ray" <ray.ni@intel.com>,
Oliver Smith-Denny <osde@linux.microsoft.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"t@taylorbeebe.com" <t@taylorbeebe.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD Capabilities With Page Table Attributes
Date: Fri, 2 Jun 2023 11:31:03 +0200 [thread overview]
Message-ID: <CAMj1kXEdPM4nhit251qg0gw6PsZ=HbE_SNP1pHS=uG7ERtGRsA@mail.gmail.com> (raw)
In-Reply-To: <da72811f-6922-9e20-d865-86526c6d99e5@linux.microsoft.com>
On Fri, 2 Jun 2023 at 05:10, Michael Kubacki
<mikuback@linux.microsoft.com> wrote:
>
> Sounds good, thanks for the quick response. Can you please send a
> calendar invite when you get a chance?
>
> On 6/1/2023 10:42 PM, Ni, Ray wrote:
> > It's a good idea to have a focus area ("project") for everyone working together on the same problem.
> > I see the benefit of having "project" is to align everyone's priority so the "project" can be done within a certain deadline.
> >
> > Let's talk more about following items in next meeting:
> > 1. Alignment of the problem to solve
> > 2. Alignment of the priority
> >
> > I am available at 10pm~11pm (GMT+8) next Wednesday night.
> >
This works for me as well.
next prev parent reply other threads:[~2023-06-02 9:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 0:09 [edk2-devel][PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD Capabilities With Page Table Attributes Oliver Smith-Denny
2023-05-01 13:02 ` Ard Biesheuvel
2023-05-01 17:03 ` Oliver Smith-Denny
2023-05-01 17:49 ` [edk2-devel] [PATCH " Michael D Kinney
2023-05-01 17:50 ` Ard Biesheuvel
2023-05-01 17:53 ` Oliver Smith-Denny
2023-05-01 17:59 ` Michael D Kinney
2023-05-09 1:35 ` Ni, Ray
2023-05-09 2:03 ` Oliver Smith-Denny
2023-05-09 2:04 ` Michael D Kinney
2023-05-09 6:59 ` Ard Biesheuvel
2023-05-09 14:59 ` Oliver Smith-Denny
2023-05-10 16:10 ` Taylor Beebe
2023-05-16 2:53 ` Ni, Ray
2023-05-16 17:11 ` Oliver Smith-Denny
2023-05-17 7:14 ` Ni, Ray
2023-06-02 2:24 ` Michael Kubacki
2023-06-02 2:42 ` Ni, Ray
2023-06-02 3:09 ` Michael Kubacki
2023-06-02 9:31 ` Ard Biesheuvel [this message]
2023-06-06 2:13 ` Michael Kubacki
2023-06-06 3:00 ` Ni, Ray
[not found] <1759538694580A69.7408@groups.io>
2023-06-07 16:10 ` [edk2-devel][PATCH " Oliver Smith-Denny
2023-06-07 17:31 ` Ard Biesheuvel
2023-06-07 18:03 ` Oliver Smith-Denny
[not found] ` <176672827230FBF7.32008@groups.io>
2023-07-07 20:13 ` Oliver Smith-Denny
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-list 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='CAMj1kXEdPM4nhit251qg0gw6PsZ=HbE_SNP1pHS=uG7ERtGRsA@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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