public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Abdul Lateef Attar via groups.io" <AbdulLateef.Attar=amd.com@groups.io>
To: Sunil V L <sunilvl@ventanamicro.com>,
	Sami Mujawar <sami.mujawar@arm.com>
Cc: devel@edk2.groups.io, Pierre.Gondois@arm.com,
	YeoReum.Yun@arm.com, jeshuas@nvidia.com, jbrasen@nvidia.com,
	gmahadevan@nvidia.com, quic_llindhol@quicinc.com,
	meenakshi.aggarwal@nxp.com, Akanksha.Jain2@arm.com,
	Sibel.Allinson@arm.com, nd@arm.com
Subject: Re: [edk2-devel] [staging/dynamictables-reorg PATCH v1 0/2] DynamicTablesPkg: Arch Common Namespace
Date: Tue, 5 Mar 2024 16:39:05 +0530	[thread overview]
Message-ID: <4f5a12b3-608d-4b10-beec-5f8f95cc35b1@amd.com> (raw)
In-Reply-To: <Zeb5dwKLfUAT8bQ4@sunil-laptop>

Hi Sami, Sunil,

     Yesterday I submitted few patches on main branch; I'll port those 
changes to this staging branch.

Currently from AMD X64 perspective I'm working on ACPI tables, once that 
is done, then will move to smbios tables.

Thanks

AbduL


On 05-03-2024 16:22, Sunil V L wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> Hi Sami,
>
> On Mon, Mar 04, 2024 at 04:46:15PM +0000, Sami Mujawar wrote:
>> This series is an initial proposal for introducing an Arch Common
>> namespace. Based on the mailing list discussions, further patch
>> series to move the configuration manager objects to the Arch
>> Common namespace and the corresponding platform support patches
>> shall be submitted for review.
>>
>> The changes can be seen at:
>> https://github.com/samimujawar/edk2/tree/3007_dynamictables_reorg_arch_namespace_v1
>>
> Looks good to me.
>
> Reviewed-by: Sunil V L <sunilvl@ventanamicro.com>
>
> How do we plan creating further patches? I am fine with any approach you
> suggest but don't want to duplicate effort. I think it would be helpful
> to know whether someone is already working on it.
>
> Thanks!
> Sunil


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116362): https://edk2.groups.io/g/devel/message/116362
Mute This Topic: https://groups.io/mt/104726066/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-03-05 11:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 16:46 [edk2-devel] [staging/dynamictables-reorg PATCH v1 0/2] DynamicTablesPkg: Arch Common Namespace Sami Mujawar
2024-03-04 16:46 ` [edk2-devel] [staging/dynamictables-reorg PATCH v1 1/2] DynamicTablesPkg: Introduce an " Sami Mujawar
2024-03-05 10:42   ` Sunil V L
2024-03-05 11:00     ` Sami Mujawar
2024-03-04 16:46 ` [edk2-devel] [staging/dynamictables-reorg PATCH v1 2/2] DynamicTablesPkg: Identify common Arm namespace objects Sami Mujawar
2024-03-05  8:44 ` [edk2-devel] [staging/dynamictables-reorg PATCH v1 0/2] DynamicTablesPkg: Arch Common Namespace PierreGondois
2024-03-05  9:45   ` Sami Mujawar
2024-03-05 10:52 ` Sunil V L
2024-03-05 11:09   ` Abdul Lateef Attar via groups.io [this message]
2024-03-05 14:03     ` PierreGondois
2024-03-05 14:13       ` Abdul Lateef Attar via groups.io
2024-03-11 14:35   ` Sami Mujawar
2024-03-12  5:26     ` Sunil V L

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=4f5a12b3-608d-4b10-beec-5f8f95cc35b1@amd.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