Laszlo Ersek writes:
> On 11/29/13 14:57, Markus Armbruster wrote:
>> Laszlo Ersek writes:
>>
>>> The blob is 64K in size and contains 0x00..0xFF repeatedly.
>>>
>>> The client code added to main() wouldn't make much sense in the long term.
>>> It helps with debugging and it silences gcc about
Il 29/11/2013 16:07, Laszlo Ersek ha scritto:
> I think that the way I did it here matches this situation well. After
> the g_file_open_tmp() call succeeds, we must close fd in any case
> (independently of whether as a whole the function succeeds or not).
> Optionally, we must also unlink the file,
On 11/29/13 14:57, Markus Armbruster wrote:
> Laszlo Ersek writes:
>
>> The blob is 64K in size and contains 0x00..0xFF repeatedly.
>>
>> The client code added to main() wouldn't make much sense in the long term.
>> It helps with debugging and it silences gcc about create_firmware() being
>> unus
Laszlo Ersek writes:
> The blob is 64K in size and contains 0x00..0xFF repeatedly.
>
> The client code added to main() wouldn't make much sense in the long term.
> It helps with debugging and it silences gcc about create_firmware() being
> unused, and we'll replace it in the next patch anyway.
>
The blob is 64K in size and contains 0x00..0xFF repeatedly.
The client code added to main() wouldn't make much sense in the long term.
It helps with debugging and it silences gcc about create_firmware() being
unused, and we'll replace it in the next patch anyway.
Signed-off-by: Laszlo Ersek
---
