public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	edk2-devel@lists.01.org,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Andrew Fish <afish@apple.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Steve.Capper@arm.com
Subject: Re: [PATCH] Maintainers.txt: update OvmfPkg maintainership
Date: Thu, 17 Aug 2017 13:57:21 +0200	[thread overview]
Message-ID: <2871a0d3-4457-beaa-de1d-f48eb0b9cd93@redhat.com> (raw)
In-Reply-To: <20170817101214.abtzjjngs2gxn3r6@bivouac.eciton.net>

On 08/17/17 12:12, Leif Lindholm wrote:
> On Thu, Aug 17, 2017 at 01:47:59AM +0200, Laszlo Ersek wrote:
>> On 08/17/17 00:37, Jordan Justen wrote:
>>> On 2017-08-16 12:23:49, Leif Lindholm wrote:
>>
>> [snip]
>>
>>>> - the value proposition
>>>> for Linaro is that having maintainer parity ArmVirtPkg/OvmfPkg
>>>> simplifies the task of maintaining feature parity between the two.
>>>> (It is no secret that I would love to see them as a single package,
>>>> making it easier to clean up the way EDK2-for-qemu gets packaged by
>>>> Linux distributions.)
>>>
>>> I would also prefer to have OVMF support ARM and eventually RISC-V as
>>> well. I don't think Laszlo feels as confident about this though.
>>
>> I have two concerns:
>>
>> (1) Reorganizing OvmfPkg for this would take an immense amount of time
>> (with possible regressions).
> 
> Well, I'm the one who keeps pushing for it, so it'd be impolite of me
> to suggest that someone else should have to deal with it.
> 
>> (2) Sharing more code between modules that aren't inherently
>> architecture-independent (and virtualization platform-independent) is risky.
> 
> Let me start by clarifying what I would like to see:
> - ArmVirtPkg and OvmfPkg merged into one package.
> - Merging a lot of common items into shared .dsc.inc and .fdf.inc
>   across all platforms.
> - ARM/AARCH64 platforms added to build.sh/create-release.py.
> - End.

OK, this sounds a lot more palatable to me than unifying actual code.

Thanks!
Laszlo


  reply	other threads:[~2017-08-17 11:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 17:17 [PATCH] Maintainers.txt: update OvmfPkg maintainership Leif Lindholm
2017-08-16 17:23 ` Kinney, Michael D
2017-08-16 18:02 ` Laszlo Ersek
2017-08-16 19:17   ` Ard Biesheuvel
2017-08-16 18:09 ` Jordan Justen
2017-08-16 18:26   ` Laszlo Ersek
2017-08-16 19:23   ` Leif Lindholm
2017-08-16 22:37     ` Jordan Justen
2017-08-16 23:47       ` Laszlo Ersek
2017-08-17 10:12         ` Leif Lindholm
2017-08-17 11:57           ` Laszlo Ersek [this message]
2017-08-23  1:30         ` Konrad Rzeszutek Wilk
2017-08-23  9:04           ` Laszlo Ersek
2017-08-23  9:17             ` Wei Liu

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=2871a0d3-4457-beaa-de1d-f48eb0b9cd93@redhat.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