public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Hao A" <hao.a.wu@intel.com>
To: David Woodhouse <dwmw2@infradead.org>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Ni, Ray" <ray.ni@intel.com>, Laszlo Ersek <lersek@redhat.com>,
	"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
	"Phillips, D Scott" <d.scott.phillips@intel.com>
Subject: Re: [PATCH v2 0/6] Ovmf: Drop IntelFramework[Module]Pkg dependency
Date: Tue, 11 Jun 2019 07:49:30 +0000	[thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8E4FAF@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <453b7e3c48014bd651717ccf9d9380356530bc82.camel@infradead.org>

> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: Tuesday, June 11, 2019 3:37 PM
> To: Justen, Jordan L; Wu, Hao A; devel@edk2.groups.io
> Cc: Ni, Ray; Laszlo Ersek; Ard Biesheuvel; Phillips, D Scott
> Subject: Re: [PATCH v2 0/6] Ovmf: Drop IntelFramework[Module]Pkg
> dependency
> 
> On Tue, 2019-06-11 at 00:35 -0700, Jordan Justen wrote:
> > I see that https://bugzilla.tianocore.org/show_bug.cgi?id=1811
> > mentions that there is "missing of reviewer/maintainer of the CSM
> > modules in OvmfPkg", so it will be dropped. Yet, I thought David
> > agreed to maintain that support as recently as May 20:
> >
> > https://edk2.groups.io/g/devel/message/41049
> >
> > Maybe he changed his mind about it?
> 
> No, I'm happy to do it. Just been fairly busy recently.
> 
> There appears to be nothing actually on fire this week. I may actually
> get to spend some quality time making sure it works again.

Hello all,

For the series:
[PATCH v2 00/10] Duplicate required CSM components for OVMF
https://edk2.groups.io/g/devel/message/41385

I sent it out on May 27th, and did not receive a confirmation from David
for about 2 weeks. I think maybe the CSM support on OVMF is no longer
cared, and thus I sent another series today to drop such support: 
[PATCH v1 0/2] OVMF: Drop CSM support
https://edk2.groups.io/g/devel/message/42142

Please help to provide some feedbacks/confirmation on what should I do for
the next step. (This task actually blocks our proposal to remove
IntelFramework[Module]Pkg from edk2.)

Thanks in advance.

Best Regards,
Hao Wu


  reply	other threads:[~2019-06-11  7:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  1:43 [PATCH v2 0/6] Ovmf: Drop IntelFramework[Module]Pkg dependency Wu, Hao A
2019-06-11  1:43 ` [PATCH v2 1/6] OvmfPkg/PlatformPei: Remove redundant reference of framework pkg DEC Wu, Hao A
2019-06-11  1:43 ` [PATCH v2 2/6] OvmfPkg/OvmfPkg.dec: Add PcdShellFile in OVMF DEC file Wu, Hao A
2019-06-11  1:43 ` [PATCH v2 3/6] OvmfPkg/PlatformBootManagerLib: Use PcdShellFile defined in OvmfPkg Wu, Hao A
2019-06-11  1:43 ` [PATCH v2 4/6] OvmfPkg/DSC: Remove the consume of PcdShellFile in framework package Wu, Hao A
2019-06-11  1:43 ` [PATCH v2 5/6] OvmfPkg: Copy LegacyBios protocol definitions from IntelFrameworkPkg Wu, Hao A
2019-06-11  1:43 ` [PATCH v2 6/6] OvmfPkg/IncompatiblePciDeviceSupportDxe: Drop framework pkg dependency Wu, Hao A
2019-06-11  6:49 ` [PATCH v2 0/6] Ovmf: Drop IntelFramework[Module]Pkg dependency Ard Biesheuvel
2019-06-11  7:35 ` Jordan Justen
2019-06-11  7:37   ` David Woodhouse
2019-06-11  7:49     ` Wu, Hao A [this message]
2019-06-11  8:01       ` David Woodhouse
2019-06-11  8:06         ` Wu, Hao A
2019-06-12  1:19         ` Wu, Hao A
2019-06-12  2:04           ` Ni, Ray
2019-06-12  2:13             ` Wu, Hao A
2019-06-12  7:58               ` Laszlo Ersek
2019-06-12  8:03                 ` David Woodhouse
2019-06-12 11:52                   ` Laszlo Ersek
2019-06-12 12:08                     ` [edk2-devel] " David Woodhouse
2019-06-13  5:47                       ` Wu, Hao A
2019-06-12 15:15                     ` David Woodhouse
2019-06-12 16:28                       ` Laszlo Ersek
2019-06-12  9:50                 ` [edk2-devel] " Ni, Ray

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=B80AF82E9BFB8E4FBD8C89DA810C6A093C8E4FAF@SHSMSX104.ccr.corp.intel.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