public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chiu, Chasel" <chasel.chiu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"spbrogan@outlook.com" <spbrogan@outlook.com>
Cc: "Ma, Maurice" <maurice.ma@intel.com>,
	"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
	"Zeng, Star" <star.zeng@intel.com>
Subject: Re: [edk2-devel] [PATCH] IntelFsp2Pkg: Add Fsp22SecCoreS.inf to Dsc.
Date: Wed, 10 Jun 2020 13:41:49 +0000	[thread overview]
Message-ID: <SN6PR11MB281455E91289DEC5ACADCD2EE6830@SN6PR11MB2814.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN8PR07MB6962971B4C17FD8075AAA404C8830@BN8PR07MB6962.namprd07.prod.outlook.com>


Thanks Sean and I will correct the copyright typo.
We will evaluate Core CI enabling.

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Sean
> Sent: Wednesday, June 10, 2020 2:55 PM
> To: devel@edk2.groups.io; Chiu, Chasel <chasel.chiu@intel.com>
> Cc: Ma, Maurice <maurice.ma@intel.com>; Desimone, Nathaniel L
> <nathaniel.l.desimone@intel.com>; Zeng, Star <star.zeng@intel.com>
> Subject: Re: [edk2-devel] [PATCH] IntelFsp2Pkg: Add Fsp22SecCoreS.inf to Dsc.
> 
> I think your copyright year is off.  2022?
> 
> After you fix that
> 
> Reviewed-by: Sean Brogan <sean.brogan@microsoft.com>
> 
> Also since you are the package maintainer of this package what do you think
> about enabling Core CI?  We do this already in Project Mu which is how
> this missing entry was identified.
> https://github.com/microsoft/mu_silicon_intel_tiano/blob/release/202002/I
> ntelFsp2Pkg/IntelFsp2Pkg.ci.yaml
> 
> 
> Thanks
> Sean
> 
> 
> On 6/9/2020 7:33 PM, Chiu, Chasel wrote:
> > REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2788
> >
> > DSC is incomplete according to the established CI policies.
> > Fsp22SecCoreS.inf needs to be added to the Components section for
> > completeness.
> >
> > Cc: Maurice Ma <maurice.ma@intel.com>
> > Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
> > Cc: Star Zeng <star.zeng@intel.com>
> > Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
> > ---
> >   IntelFsp2Pkg/IntelFsp2Pkg.dsc | 3 ++-
> >   1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/IntelFsp2Pkg/IntelFsp2Pkg.dsc
> > b/IntelFsp2Pkg/IntelFsp2Pkg.dsc index 02fe9cb188..9b5e38c5d9 100644
> > --- a/IntelFsp2Pkg/IntelFsp2Pkg.dsc
> > +++ b/IntelFsp2Pkg/IntelFsp2Pkg.dsc
> > @@ -1,7 +1,7 @@
> >   ## @file
> >   # Provides driver and definitions to build fsp.
> >   #
> > -# Copyright (c) 2014 - 2016, Intel Corporation. All rights
> > reserved.<BR>
> > +# Copyright (c) 2014 - 2022, Intel Corporation. All rights
> > +reserved.<BR>
> >   # SPDX-License-Identifier: BSD-2-Clause-Patent
> >   #
> >   ##
> > @@ -65,6 +65,7 @@
> >     IntelFsp2Pkg/FspSecCore/FspSecCoreT.inf
> >     IntelFsp2Pkg/FspSecCore/FspSecCoreM.inf
> >     IntelFsp2Pkg/FspSecCore/FspSecCoreS.inf
> > +  IntelFsp2Pkg/FspSecCore/Fsp22SecCoreS.inf
> >     IntelFsp2Pkg/FspNotifyPhase/FspNotifyPhasePeim.inf
> >
> >   [PcdsFixedAtBuild.common]
> >
> 
> 


  reply	other threads:[~2020-06-10 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  2:33 [PATCH] IntelFsp2Pkg: Add Fsp22SecCoreS.inf to Dsc Chiu, Chasel
2020-06-10  6:54 ` [edk2-devel] " Sean
2020-06-10 13:41   ` Chiu, Chasel [this message]
2020-06-10 20:35 ` Nate DeSimone
2020-06-11 11:20   ` Zeng, Star

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=SN6PR11MB281455E91289DEC5ACADCD2EE6830@SN6PR11MB2814.namprd11.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