Hi Quentin,
On 3 January 2018 at 02:18, Quentin Schulz
wrote:
> Hi Simon,
>
> On 29/12/2017 04:13, Simon Glass wrote:
>> Hi Quentin,
>>
>> On 22 December 2017 at 14:13, Quentin Schulz
>> wrote:
>>> This patch series is based on this[1] patch series from Maxime.
>>>
>>> This is an RFC. It's been
Hi Simon,
On 29/12/2017 04:13, Simon Glass wrote:
> Hi Quentin,
>
> On 22 December 2017 at 14:13, Quentin Schulz
> wrote:
>> This patch series is based on this[1] patch series from Maxime.
>>
>> This is an RFC. It's been only tested in a specific use case on a custom
>> i.MX6 board. It's known t
Hi Quentin,
On 22 December 2017 at 14:13, Quentin Schulz
wrote:
> This patch series is based on this[1] patch series from Maxime.
>
> This is an RFC. It's been only tested in a specific use case on a custom
> i.MX6 board. It's known to break compilation on a few boards.
>
> I have a use case wher
Hi Quentin,
> 2) Why do we consider ENV_IS_NOWHERE an invalid environment? The only
> place I found a use for it was to just say that if the environment is
> invalid, we should set to default environment (in env_relocate in
> env/common.c). With my patch series I guess that we could remove this
>
This patch series is based on this[1] patch series from Maxime.
This is an RFC. It's been only tested in a specific use case on a custom
i.MX6 board. It's known to break compilation on a few boards.
I have a use case where we want some variables from a first environment to
be overriden by variabl
5 matches
Mail list logo
