From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Fu Siyuan <siyuan.fu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Julien Grall <julien.grall@linaro.org>
Subject: Re: [PATCH v3 1/1] ArmVirtPkg: Replace obsoleted network drivers from platform DSC/FDF.
Date: Tue, 6 Nov 2018 17:39:02 +0100 [thread overview]
Message-ID: <CAKv+Gu_5SdpVRhdzYpDf3Y-1-awzzuW67H9P_cCu1UPUstu4-Q@mail.gmail.com> (raw)
In-Reply-To: <7ab7d41e-ec48-3fb2-28a7-83c7471d7d0e@redhat.com>
On 6 November 2018 at 16:24, Laszlo Ersek <lersek@redhat.com> wrote:
> On 11/06/18 13:32, Ard Biesheuvel wrote:
>> On 6 November 2018 at 02:24, Fu Siyuan <siyuan.fu@intel.com> wrote:
>>> V3:
>>> Remove duplicate library added in v2 patch, since ArmVirtPkg.dsc.inc
>>> already have them. Just remove the if...end there is enough.
>>>
>>> V2:
>>> Add missing library instance for NetworkPkg iSCSI driver.
>>>
>>
>> Please don't put the patch revision history in the commit log. Put it
>> below the ---
>>
>>> This patch replaces the MdeModulePkg TCP, PXE and iSCSI driver with those
>>> ones in NetworkPkg. These 3 drivers in MdeModulePkg are not being actively
>>> maintained and will be removed from edk2 master soon.
>>>
>>> Cc: Laszlo Ersek <lersek@redhat.com>
>>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>> Cc: Julien Grall <julien.grall@linaro.org>
>>> Contributed-under: TianoCore Contribution Agreement 1.1
>>> Signed-off-by: Fu Siyuan <siyuan.fu@intel.com>
>>> ---
>>
>> ... here ...
>>
>> The patch looks fine to me
>>
>> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>
>> but please don't merge it until after the next stable tag has been created
>
> This is not a bad idea (see also your discussion with Leif); however it
> does create a bit of inconsistency with how the other platform DSC/FDF
> files have been handled. (The changes have been pushed for those.)
>
> Again, I don't disagree, and I don't mind if ArmVirt is handled
> differently. It's just that we should have handled this more uniformly,
> I believe.
>
Yes - as I replied to Leif, I am not going to obsess about this. But
the point of stable tags is not to rush things in at the last minute.
>
> In retrospect, I would have also appreciated if the patches had
> referenced <https://bugzilla.tianocore.org/show_bug.cgi?id=1278>, even
> though they only implement "prep" work for now, on the platform DSC/FDF
> level, and not the actual driver removal.
>
> For example, the important explanation about MdeModulePkg's iSCSI driver
> implementing its own MD5 algo cannot be connected to the OVMF commit now
> (d2f1f6423bd1). I have copied the most relevant passage from the cover
> letter of this series into TianoCore BZ#1278, but the commit in question
> doesn't reference any BZ, so the link cannot be established.
>
> Thanks
> Laszlo
next prev parent reply other threads:[~2018-11-06 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 1:24 [PATCH v3 0/1] Delete TCP, PXE, iSCSI driver in MdeModulePkg Fu Siyuan
2018-11-06 1:24 ` [PATCH v3 1/1] ArmVirtPkg: Replace obsoleted network drivers from platform DSC/FDF Fu Siyuan
2018-11-06 12:32 ` Ard Biesheuvel
2018-11-06 15:24 ` Laszlo Ersek
2018-11-06 16:39 ` Ard Biesheuvel [this message]
2018-11-07 0:58 ` Fu, Siyuan
2018-12-14 6:11 ` Fu, Siyuan
2018-12-14 7:22 ` Ard Biesheuvel
2018-11-06 15:18 ` Laszlo Ersek
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=CAKv+Gu_5SdpVRhdzYpDf3Y-1-awzzuW67H9P_cCu1UPUstu4-Q@mail.gmail.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