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: Zhichao Gao <zhichao.gao@intel.com>,
	Maciej Rabeda <maciej.rabeda@linux.intel.com>,
	Jiaxin Wu <jiaxin.wu@intel.com>, Siyuan Fu <siyuan.fu@intel.com>,
	Ray Ni <ray.ni@intel.com>, Liming Gao <liming.gao@intel.com>,
	Nd <nd@arm.com>,
	Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [PATCH v11 0/1] ShellPkg/DynamicCommand: add HttpDynamicCommand
Date: Fri, 11 Sep 2020 09:19:31 +0200	[thread overview]
Message-ID: <b141d27c-39df-e96f-4c56-55f18c2035f1@redhat.com> (raw)
In-Reply-To: <e83a6e33a6ee1d83a8ad8e660f0a5036@mail.gmail.com>

On 09/10/20 22:33, Vladimir Olovyannikov wrote:
> Hi Laszlo,
>
>> -----Original Message-----
>> From: Laszlo Ersek <lersek@redhat.com>
>> Sent: Wednesday, September 9, 2020 11:33 PM

>>> PATCH v11 changes:
>>> Address comments from Laszlo:
>>>   - use TimeBaseLib.h header to get rid of duplicated constants;
>>>   - explicitly return UINT32 in EfiTimeToEpoch().
>>
>> to be clear, I explicitly *disagree* with returning UINT32 from
>> EfiTimeToEpoch().
>>
>> I'm not "demanding" (or even suggesting) that you update the
>> EfiTimeToEpoch() implementation in this patch to return UINTN, but
>> I'd like to be very clear that, IMO, for EfiTimeToEpoch() to suffer
>> from a year 2106 problem on 64-bit systems too, is bad design. So
>> please don't list the UINT32 return type as my suggestion -- that's
>> the exact opposite of what I'd actually suggest.

> Sorry, I must have misunderstood. Do you want me to resubmit the
> patch? I am open to ideas.

Ideally:

- change the return type of EfiTimeToEpoch() to UNITN

- drop the final UINT32 cast from EfiTimeToEpoch()

- change the type of ElapsedSeconds to UINTN

- change the expression

    ElapsedSeconds > 1 ? ElapsedSeconds : 1

  to

    ElapsedSeconds > 1 ? (UINT64)ElapsedSeconds : 1

- print the expression mentioned above with the format specifier %Lu

*BUT*. These are really just small details. It would be OK to fix these
up later, incrementally. Where I see a real problem is the lack of
timely feedback from the ShellPkg maintainers.

Laszlo


  reply	other threads:[~2020-09-11  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 18:49 [PATCH v11 0/1] ShellPkg/DynamicCommand: add HttpDynamicCommand Vladimir Olovyannikov
2020-09-09 18:49 ` [PATCH v11 1/1] " Vladimir Olovyannikov
2020-09-10  6:32 ` [PATCH v11 0/1] " Laszlo Ersek
2020-09-10 20:33   ` Vladimir Olovyannikov
2020-09-11  7:19     ` Laszlo Ersek [this message]
2020-09-11 17:04       ` Vladimir Olovyannikov
2020-09-14  0:51         ` Gao, Zhichao
2020-09-14  4:37           ` Vladimir Olovyannikov
2020-09-14  8:19             ` Gao, Zhichao
2020-09-14 18:54               ` Vladimir Olovyannikov

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=b141d27c-39df-e96f-4c56-55f18c2035f1@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