public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
	"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 09:01:14 +0100	[thread overview]
Message-ID: <abc1db5b19a72e79fb481c381d06d7af3057515d.camel@infradead.org> (raw)
In-Reply-To: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8E4FAF@SHSMSX104.ccr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

On Tue, 2019-06-11 at 07:49 +0000, Wu, Hao A wrote:
> 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.)


Apologies for the delay. It wasn't clear that the first series was
actually tested by booting with a CSM, and I was reluctant to ack it
without knowing that it didn't cause a regression.

This is, of course, complicated by the fact that I can't actually get a
CSM boot to complete at the moment. But it gets a long way into the
boot process before something goes wrong, so confirmation that it still
gets at least that far with your 'Duplicate required CSM components'
series would be good.

Is there a git tree I can pull from? I seem to recall that last time I
spent serious time working on OVMF, life was horribly complicated by
CRLF line endings, and it was extremely painful to just apply patches
from email... is that still the case?



[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]

  reply	other threads:[~2019-06-11  8:01 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
2019-06-11  8:01       ` David Woodhouse [this message]
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=abc1db5b19a72e79fb481c381d06d7af3057515d.camel@infradead.org \
    --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