On Wednesday 05 August 2009 17:26:50 Ben Warren wrote:
> Wolfgang Denk wrote:
> > Mike Frysinger wrote:
> >> In the previous enetaddr refactoring, the assumption with commit
> >> 56b555a644 was that the eth layer would handle the env -> device
> >> enetaddr syncing. This was not the case as eth_ini
Mike,
Mike Frysinger wrote:
> In the previous enetaddr refactoring, the assumption with commit 56b555a644
> was that the eth layer would handle the env -> device enetaddr syncing.
> This was not the case as eth_initialize() is called only once and the sync
> occurs there. So make sure the eth_ini
Wolfgang Denk wrote:
> Dear Ben,
>
> In message <1247707888-5415-1-git-send-email-vap...@gentoo.org> Mike
> Frysinger wrote:
>
>> In the previous enetaddr refactoring, the assumption with commit 56b555a644
>> was that the eth layer would handle the env -> device enetaddr syncing.
>> This was no
Dear Ben,
In message <1247707888-5415-1-git-send-email-vap...@gentoo.org> Mike Frysinger
wrote:
> In the previous enetaddr refactoring, the assumption with commit 56b555a644
> was that the eth layer would handle the env -> device enetaddr syncing.
> This was not the case as eth_initialize() is ca
> In the previous enetaddr refactoring, the assumption with commit 56b555a644
> was that the eth layer would handle the env -> device enetaddr syncing.
> This was not the case as eth_initialize() is called only once and the sync
> occurs there. So make sure the eth_init() function does the env ->
In the previous enetaddr refactoring, the assumption with commit 56b555a644
was that the eth layer would handle the env -> device enetaddr syncing.
This was not the case as eth_initialize() is called only once and the sync
occurs there. So make sure the eth_init() function does the env -> device
s
6 matches
Mail list logo
