On Mar 6, 2011, at 10:16 PM, Kumar Gala wrote:
> We don't use disable_law in the SPL code so only build it if
> !CONFIG_NAND_SPL.
>
> Signed-off-by: Kumar Gala
> ---
> drivers/misc/fsl_law.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
not need, fixed by --gc-sections / -ffunct
On Mar 14, 2011, at 1:27 AM, Wolfgang Denk wrote:
> Dear Kumar Gala,
>
> In message you
> wrote:
>>
We don't use disable_law in the SPL code so only build it if
!CONFIG_NAND_SPL.
>>>
>>> Does -ffunction-sections / --gc-sections not catch this automatically?
>>
>> Doesn't appear to
Dear Kumar Gala,
In message you wrote:
>
> >> We don't use disable_law in the SPL code so only build it if
> >> !CONFIG_NAND_SPL.
> >
> > Does -ffunction-sections / --gc-sections not catch this automatically?
>
> Doesn't appear to, but not sure if the NAND makefiles are utilizing those
> optio
On Mar 13, 2011, at 4:40 PM, Wolfgang Denk wrote:
> Dear Kumar Gala,
>
> In message <1299471395-26596-1-git-send-email-ga...@kernel.crashing.org> you
> wrote:
>> We don't use disable_law in the SPL code so only build it if
>> !CONFIG_NAND_SPL.
>
> Does -ffunction-sections / --gc-sections not c
Dear Kumar Gala,
In message <1299471395-26596-1-git-send-email-ga...@kernel.crashing.org> you
wrote:
> We don't use disable_law in the SPL code so only build it if
> !CONFIG_NAND_SPL.
Does -ffunction-sections / --gc-sections not catch this automatically?
Best regards,
Wolfgang Denk
--
DENX S
We don't use disable_law in the SPL code so only build it if
!CONFIG_NAND_SPL.
Signed-off-by: Kumar Gala
---
drivers/misc/fsl_law.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/misc/fsl_law.c b/drivers/misc/fsl_law.c
index 3233ff2..9b25ddc 100644
--- a/driver
6 matches
Mail list logo