public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>,
	devel@edk2.groups.io
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Leif Lindholm <leif@nuviainc.com>
Subject: Re: [PATCH 2/2] OvmfPkg: enable HttpDynamicCommand
Date: Thu, 23 Jul 2020 12:37:53 +0200	[thread overview]
Message-ID: <2b6ebe53-57b1-7fc2-2f42-8add262fc9c4@redhat.com> (raw)
In-Reply-To: <4767b4be3123d81816ad90be93e67f1b@mail.gmail.com>

On 07/22/20 22:02, Vladimir Olovyannikov wrote:
> Hi Laszlo,
> 
> Thank you for reviewing the patchset.

Thank *you* for submitting the set, at my request! :)

>> -----Original Message-----
>> From: Laszlo Ersek <lersek@redhat.com>
>> Sent: Wednesday, July 22, 2020 12:52 PM
>> To: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>;
>> devel@edk2.groups.io
>> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>; Leif Lindholm
>> <leif@nuviainc.com>
>> Subject: Re: [PATCH 2/2] OvmfPkg: enable HttpDynamicCommand
>>
>> On 07/21/20 19:23, Vladimir Olovyannikov wrote:
>>> Enable HttpDynamicCommand (Shell command "http") for OvmfPkg
>> platforms
>>>
>>> Signed-off-by: Vladimir Olovyannikov
>>> <vladimir.olovyannikov@broadcom.com>
>>> ---
>>>  OvmfPkg/OvmfPkgIa32.dsc    | 6 ++++++
>>>  OvmfPkg/OvmfPkgIa32X64.dsc | 6 ++++++
>>>  OvmfPkg/OvmfPkgX64.dsc     | 6 ++++++
>>>  OvmfPkg/OvmfXen.dsc        | 6 ++++++
>>>  4 files changed, 24 insertions(+)
>>>
>>> diff --git a/OvmfPkg/OvmfPkgIa32.dsc b/OvmfPkg/OvmfPkgIa32.dsc index
>>> 9178ffeb71cb..aed3a73c0172 100644
>>> --- a/OvmfPkg/OvmfPkgIa32.dsc
>>> +++ b/OvmfPkg/OvmfPkgIa32.dsc
>>> @@ -883,6 +883,12 @@ [Components]
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>>    }
>>> +
>>> +
>> ShellPkg/DynamicCommand/HttpDynamicCommand/HttpDynamicCommand
>> .inf {
>>> +    <PcdsFixedAtBuild>
>>> +      gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>> +  }
>>> +
>>>
>> OvmfPkg/LinuxInitrdDynamicShellCommand/LinuxInitrdDynamicShellComma
>> nd.inf {
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>> diff --git a/OvmfPkg/OvmfPkgIa32X64.dsc
>> b/OvmfPkg/OvmfPkgIa32X64.dsc
>>> index a665f78f0dc7..6c07326cc0fe 100644
>>> --- a/OvmfPkg/OvmfPkgIa32X64.dsc
>>> +++ b/OvmfPkg/OvmfPkgIa32X64.dsc
>>> @@ -897,6 +897,12 @@ [Components.X64]
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>>    }
>>> +
>>> +
>> ShellPkg/DynamicCommand/HttpDynamicCommand/HttpDynamicCommand
>> .inf {
>>> +    <PcdsFixedAtBuild>
>>> +      gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>> +  }
>>> +
>>>
>> OvmfPkg/LinuxInitrdDynamicShellCommand/LinuxInitrdDynamicShellComma
>> nd.inf {
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>> diff --git a/OvmfPkg/OvmfPkgX64.dsc b/OvmfPkg/OvmfPkgX64.dsc index
>>> 17f345acf4ee..d5e5bcf8e66c 100644
>>> --- a/OvmfPkg/OvmfPkgX64.dsc
>>> +++ b/OvmfPkg/OvmfPkgX64.dsc
>>> @@ -893,6 +893,12 @@ [Components]
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>>    }
>>> +
>>> +
>> ShellPkg/DynamicCommand/HttpDynamicCommand/HttpDynamicCommand
>> .inf {
>>> +    <PcdsFixedAtBuild>
>>> +      gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>> +  }
>>> +
>>>
>> OvmfPkg/LinuxInitrdDynamicShellCommand/LinuxInitrdDynamicShellComma
>> nd.inf {
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>> diff --git a/OvmfPkg/OvmfXen.dsc b/OvmfPkg/OvmfXen.dsc index
>>> 782803cb2787..fe549502863a 100644
>>> --- a/OvmfPkg/OvmfXen.dsc
>>> +++ b/OvmfPkg/OvmfXen.dsc
>>> @@ -675,6 +675,12 @@ [Components]
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>>    }
>>> +
>>> +
>> ShellPkg/DynamicCommand/HttpDynamicCommand/HttpDynamicCommand
>> .inf {
>>> +    <PcdsFixedAtBuild>
>>> +      gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>> +  }
>>> +
>>>
>> OvmfPkg/LinuxInitrdDynamicShellCommand/LinuxInitrdDynamicShellComma
>> nd.inf {
>>>      <PcdsFixedAtBuild>
>>>        gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
>>>
>>
>> Basically same comments as under the ArmVirtPkg patch:
>>
>> (1) Please mention <https://bugzilla.tianocore.org/show_bug.cgi?id=2857>
>> in the commit message.
> OK, will do. For future contributions related to a BZ ticket - does it mean
> that mentioning of BZ id in the cover letter is not enough?

Referencing the BZ in the cover letter only is indeed not ideal; the
cover letter does not get captured in the git history. When submitting a
series for a BZ, it's best to mention the BZ in every patch in the series.

One frequently used format is

"""
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2857
"""

placed near the end of the commit message (just above the Signed-off-by
and similar tags). But other formats are fine too.

>>
>> (2) Please don't introduce the extra whitespace in the DSC files.
>>
>> (3) Please also add the new module to the following (FDF) files:
>>
>> - OvmfPkgIa32.fdf
>> - OvmfPkgIa32X64.fdf
>> - OvmfPkgX64.fdf
>> - OvmfXen.fdf
> OK, will do, thanks.
>>
>> Once you post v2 of this series, with the above points fixed (especially
>> the
>> FDF files), I'd like to test the new command (with both ArmVirtQemu and
>> OVMF).
> Sure, that would be great.

Thanks!
Laszlo


      reply	other threads:[~2020-07-23 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 17:23 [PATCH 0/2] Enable HttpDynamicCommand for ArmVirtPkg and OvmfPkg Vladimir Olovyannikov
2020-07-21 17:23 ` [PATCH 1/2] ArmVirtPkg: enable HttpDynamiCommand Vladimir Olovyannikov
2020-07-22 19:47   ` Laszlo Ersek
2020-07-21 17:23 ` [PATCH 2/2] OvmfPkg: enable HttpDynamicCommand Vladimir Olovyannikov
2020-07-22 19:51   ` Laszlo Ersek
2020-07-22 20:02     ` Vladimir Olovyannikov
2020-07-23 10:37       ` Laszlo Ersek [this message]

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=2b6ebe53-57b1-7fc2-2f42-8add262fc9c4@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