On Wed, Aug 02, 2023 at 11:09:43AM -0400, Tom Rini wrote:
> It is not a parse error to have a default value of "0" for a "hex" type
> entry, instead of "0x0". However, "0" and "0x0" are not treated the
> same even by the tools themselves. Correct this by changing the default
> value from "0" to
On Wed, Aug 02, 2023 at 03:31:22PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 2 Aug 2023 at 09:10, Tom Rini wrote:
> >
> > It is not a parse error to have a default value of "0" for a "hex" type
> > entry, instead of "0x0". However, "0" and "0x0" are not treated the
> > same even by the
Hi Tom,
On Wed, 2 Aug 2023 at 09:10, Tom Rini wrote:
>
> It is not a parse error to have a default value of "0" for a "hex" type
> entry, instead of "0x0". However, "0" and "0x0" are not treated the
> same even by the tools themselves. Correct this by changing the default
> value from "0" to
It is not a parse error to have a default value of "0" for a "hex" type
entry, instead of "0x0". However, "0" and "0x0" are not treated the
same even by the tools themselves. Correct this by changing the default
value from "0" to "0x0" for all hex type questions that had the
incorrect default.
4 matches
Mail list logo
