public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chang, Abner" <abner.chang@amd.com>
To: Leif Lindholm <quic_llindhol@quicinc.com>,
	"Attar, AbdulLateef (Abdul Lateef)" <AbdulLateef.Attar@amd.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Attar, AbdulLateef (Abdul Lateef)" <AbdulLateef.Attar@amd.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [PATCH v2 RESEND 4/4] Maintainers.txt: Adds AMD/BoardPkg and AMD/PlatformPkg maintainers
Date: Sat, 18 Mar 2023 09:03:50 +0000	[thread overview]
Message-ID: <MN2PR12MB3966413C75B643BBDC214693EA829@MN2PR12MB3966.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ZBSQnlC6L/zjOOvU@qc-i7.hemma.eciton.net>

[AMD Official Use Only - General]

Hi Leif,
Thanks to your review.
AMD\PlatformPkg is mainly for the modules that are generic to AMD's server, client or other platforms, while AMD\BoardPkg that contains the modules that support MinPlatformrPkg framework. AMD\BoardPkg may also provide the modules those are common to all AMD boards and leverage by the board specific packages under AMD\BoardPkg. Perhaps AMD\Board would a better naming that contains both common board modules and the specific board packages. I don't know the context of OverdriveBoard , however we would like to see OverdriveBoard is relocated to under AMD\Board(Pkg) as well. With this we can have a well organized AMD directory under edk2-platform that provides AMD opensource edk2 solution to industry.

Thanks
Abner

> -----Original Message-----
> From: Leif Lindholm <quic_llindhol@quicinc.com>
> Sent: Saturday, March 18, 2023 12:09 AM
> To: Attar, AbdulLateef (Abdul Lateef) <AbdulLateef.Attar@amd.com>
> Cc: devel@edk2.groups.io; Attar, AbdulLateef (Abdul Lateef)
> <AbdulLateef.Attar@amd.com>; Ard Biesheuvel
> <ardb+tianocore@kernel.org>; Chang, Abner <Abner.Chang@amd.com>;
> Michael D Kinney <michael.d.kinney@intel.com>
> Subject: Re: [PATCH v2 RESEND 4/4] Maintainers.txt: Adds AMD/BoardPkg
> and AMD/PlatformPkg maintainers
> 
> Caution: This message originated from an External Source. Use proper
> caution when opening attachments, clicking links, or responding.
> 
> 
> On Fri, Mar 17, 2023 at 12:20:07 +0530, Abdul Lateef Attar wrote:
> > From: Abdul Lateef Attar <AbdulLateef.Attar@amd.com>
> >
> > Adds maintainers for AMD/BoardPkg and AMD/PlatformPkg.
> >
> > Signed-off-by: Abdul Lateef Attar <abdattar@amd.com>
> > Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> > Cc: Leif Lindholm <quic_llindhol@quicinc.com>
> > Cc: Abner Chang <abner.chang@amd.com>
> > Cc: Michael D Kinney <michael.d.kinney@intel.com>
> > ---
> >  Maintainers.txt | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/Maintainers.txt b/Maintainers.txt index
> > 747191366070..bb8ab643e090 100644
> > --- a/Maintainers.txt
> > +++ b/Maintainers.txt
> > @@ -91,6 +91,12 @@ F: Silicon/AMD/Styx/
> >  M: Ard Biesheuvel <ardb+tianocore@kernel.org>
> >  M: Leif Lindholm <quic_llindhol@quicinc.com>
> >
> > +AMD Platform
> 
> Annoyingly, I'm now going to ask the question I have been avoiding up until
> now. What does "AMD Platform" mean?
> I mean, you've placed this straight after the entry for the Seattle platforms.
> I think the name, and package names, are too generic.
> 
> /
>     Leif
> 
> > +F: Platform/AMD/BoardPkg
> > +F: Platform/AMD/PlatformPkg
> > +M: Abner Chang <abner.chang@amd.com>
> > +M: Abdul Lateef Attar <abdattar@amd.com>
> > +
> >  Ampere Computing
> >  F: Platform/Ampere
> >  F: Silicon/Ampere
> > --
> > 2.25.1
> >

  reply	other threads:[~2023-03-18  9:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  6:50 [PATCH v2 RESEND 0/4] Adds AMD/BoardPkg and AMD/PlatformPkg Abdul Lateef Attar
2023-03-17  6:50 ` [PATCH v2 RESEND 1/4] Platform/AMD: Adds BoardPkg and PlatformPkg Abdul Lateef Attar
2023-03-17 15:41   ` Leif Lindholm
2023-03-17  6:50 ` [PATCH v2 RESEND 2/4] Platform/AMD/PlatformPkg: Adds PciHotPlug init protocol implementation Abdul Lateef Attar
2023-03-17  6:52   ` Chang, Abner
2023-03-17 15:55   ` [edk2-devel] " Leif Lindholm
2023-03-20 10:01     ` Attar, AbdulLateef (Abdul Lateef)
2023-03-17  6:50 ` [PATCH v2 RESEND 3/4] Platform/AMD/BoarkPkg: Adds SetCacheMtrrLib library Abdul Lateef Attar
2023-03-17  6:52   ` Chang, Abner
2023-03-17 15:59   ` Leif Lindholm
2023-03-20 10:02     ` Attar, AbdulLateef (Abdul Lateef)
2023-03-17  6:50 ` [PATCH v2 RESEND 4/4] Maintainers.txt: Adds AMD/BoardPkg and AMD/PlatformPkg maintainers Abdul Lateef Attar
2023-03-17  6:53   ` Chang, Abner
2023-03-17 16:09   ` Leif Lindholm
2023-03-18  9:03     ` Chang, Abner [this message]
2023-03-20 12:54       ` [edk2-devel] " Leif Lindholm
2023-03-18  9:16     ` Chang, Abner
2023-03-18  9:42       ` Ard Biesheuvel
2023-03-18 15:34         ` Chang, Abner
2023-03-20 13:05       ` [edk2-devel] " Leif Lindholm
2023-03-20 14:09         ` Attar, AbdulLateef (Abdul Lateef)
2023-03-20 18:02           ` Leif Lindholm
2023-03-21  3:00             ` Attar, AbdulLateef (Abdul Lateef)
2023-03-22  9:54               ` Chang, Abner
2023-03-22 11:59                 ` Attar, AbdulLateef (Abdul Lateef)
2023-03-22 12:29                   ` Leif Lindholm
2023-03-20 10:11     ` Attar, AbdulLateef (Abdul Lateef)
2023-03-17  6:54 ` [PATCH v2 RESEND 0/4] Adds AMD/BoardPkg and AMD/PlatformPkg Chang, Abner

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=MN2PR12MB3966413C75B643BBDC214693EA829@MN2PR12MB3966.namprd12.prod.outlook.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