public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Oliver Smith-Denny" <osde@linux.microsoft.com>
To: "Ni, Ray" <ray.ni@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Sami Mujawar <sami.mujawar@arm.com>,
	Michael Kubacki <mikuback@linux.microsoft.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: Mon, 8 May 2023 19:03:05 -0700	[thread overview]
Message-ID: <df6ec108-522d-0503-8ab0-8d221e930ec2@linux.microsoft.com> (raw)
In-Reply-To: <MN6PR11MB824419C1BFF5A9C2C24C3C938C769@MN6PR11MB8244.namprd11.prod.outlook.com>

Hi Ray,

Thanks for setting up a meeting on this! We have some
conflicts on our side for this week, does it work
for everyone to have it the following Thursday
(May 18th)?

The time works for us.

Thanks,
Oliver

On 5/8/2023 6:35 PM, Ni, Ray wrote:
> All,
> Can you check if the meeting time is ok for you?
> 
> It will be in this week:
> * PDT Thursday 07:00
> * Paris Thursday 16:00
> * Shanghai Thursday 22:00
> 
> Thanks,
> Ray
> 
> 
>> -----Original Message-----
>> From: Kinney, Michael D <michael.d.kinney@intel.com>
>> Sent: Tuesday, May 2, 2023 1:59 AM
>> To: Oliver Smith-Denny <osde@linux.microsoft.com>; Ard Biesheuvel
>> <ardb@kernel.org>; devel@edk2.groups.io
>> Cc: Ni, Ray <ray.ni@intel.com>; Leif Lindholm <quic_llindhol@quicinc.com>;
>> Ard Biesheuvel <ardb+tianocore@kernel.org>; Sami Mujawar
>> <sami.mujawar@arm.com>; Michael Kubacki
>> <mikuback@linux.microsoft.com>; Sean Brogan
>> <sean.brogan@microsoft.com>; Kinney, Michael D
>> <michael.d.kinney@intel.com>
>> Subject: RE: [edk2-devel] [PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD
>> Capabilities With Page Table Attributes
>>
>> Thanks for the quick feedback.  Ray is out this week.  I will work with Ray to
>> arrange a time slot, hopefully next week that works for everyone.
>>
>> Mike
>>
>>> -----Original Message-----
>>> From: Oliver Smith-Denny <osde@linux.microsoft.com>
>>> Sent: Monday, May 1, 2023 10:53 AM
>>> To: Ard Biesheuvel <ardb@kernel.org>; devel@edk2.groups.io; Kinney,
>>> Michael D <michael.d.kinney@intel.com>
>>> Cc: Ni, Ray <ray.ni@intel.com>; Leif Lindholm <quic_llindhol@quicinc.com>;
>>> Ard Biesheuvel <ardb+tianocore@kernel.org>; Sami Mujawar
>>> <sami.mujawar@arm.com>; Michael Kubacki
>>> <mikuback@linux.microsoft.com>; Sean Brogan
>>> <sean.brogan@microsoft.com>
>>> Subject: Re: [edk2-devel] [PATCH v1 1/1] ArmPkg: CpuDxe: Sync GCD
>>> Capabilities With Page Table Attributes
>>>
>>> On 5/1/2023 10:50 AM, Ard Biesheuvel wrote:
>>>> On Mon, 1 May 2023 at 19:49, Michael D Kinney
>>>> <michael.d.kinney@intel.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> These UEFI Memory Map, GCD, and Page Table interactions can be
>>> complex and I
>>>>> agree there are some UEFI/PI spec clarifications that may help.
>>>>>
>>>>> Ray hosts a TianoCore design meeting when needed.  Do you think a
>>> meeting with
>>>>> an open discussion on these topics would help, or do we prefer to
>>> continue with
>>>>> email discussions?
>>>>>
>>>>
>>>> I'll gladly join a call to discuss this if we can find a timeslot that
>>>> works for everyone in terms of time zone. (I'm on Paris time)
>>>
>>> I also think a call would be great, I certainly would benefit from
>>> learning more here :). I'm sure various members of my team would
>>> be interested in joining, happy to be flexible on timeslot (we are
>>> generally in PST).
>>>
>>> Thanks,
>>> Oliver

  reply	other threads:[~2023-05-09  2:03 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 [this message]
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
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=df6ec108-522d-0503-8ab0-8d221e930ec2@linux.microsoft.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