Tom wrote on 26/11/2009 20:18:22:
>
> Joakim Tjernlund wrote:
> >> From: Alessandro Rubini
> >>
> >> While it's a matter of personal taste, I prefer to avoid ifdef when
> >> possible. For example, I don't like to add BOARD_LATE_INIT in the
> >> config file just to add a board_late_init() functio
Joakim Tjernlund wrote:
>> From: Alessandro Rubini
>>
>> While it's a matter of personal taste, I prefer to avoid ifdef when
>> possible. For example, I don't like to add BOARD_LATE_INIT in the
>> config file just to add a board_late_init() function.
>> Also, I think the file is more readable wit
Alessandro Rubini wrote:
> From: Alessandro Rubini
>
> While it's a matter of personal taste, I prefer to avoid ifdef when
> possible. For example, I don't like to add BOARD_LATE_INIT in the
> config file just to add a board_late_init() function.
> Also, I think the file is more readable without
>
> From: Alessandro Rubini
>
> While it's a matter of personal taste, I prefer to avoid ifdef when
> possible. For example, I don't like to add BOARD_LATE_INIT in the
> config file just to add a board_late_init() function.
> Also, I think the file is more readable without the ifdef stuff.
> This
From: Alessandro Rubini
While it's a matter of personal taste, I prefer to avoid ifdef when
possible. For example, I don't like to add BOARD_LATE_INIT in the
config file just to add a board_late_init() function.
Also, I think the file is more readable without the ifdef stuff.
This uses two trivi
5 matches
Mail list logo