[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFECyb_wUphr4XOyW9tC-Rw5Py3m39e6GQorCtFGtSXTUTBnFQ@mail.gmail.com>
Date: Fri, 14 Feb 2014 11:02:49 -0800
From: Roy Franz <roy.franz@...aro.org>
To: Matt Fleming <matt@...sole-pimps.org>
Cc: Leif Lindholm <leif.lindholm@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
Patch Tracking <patches@...aro.org>
Subject: Re: [PATCH 06/22] Add helper functions used by arm/arm64
On Thu, Feb 13, 2014 at 3:26 AM, Matt Fleming <matt@...sole-pimps.org> wrote:
> On Wed, 05 Feb, at 05:03:57PM, Leif Lindholm wrote:
>> From: Roy Franz <roy.franz@...aro.org>
>>
>> Add the get_dram_base() function and efi_call_physN() macros
>> that are shared by arm/arm64.
>>
>> Signed-off-by: Roy Franz <roy.franz@...aro.org>
>> Signed-off-by: Leif Lindholm <leif.lindholm@...aro.org>
>> ---
>> drivers/firmware/efi/efi-stub-helper.c | 63 +++++++++++++++++++++++++-------
>> 1 file changed, 50 insertions(+), 13 deletions(-)
>
> These changes should be in drivers/firmware/efi/arm-stub.c -
> efi-stub-helper.c is not a dumping ground for random
> architecture-specific code.
Hi Matt,
I will move those functions/macros to the arm-stub.c file. I agree
that the macros should go there, as they are the arm specific versions
and conflict with the x86 versions defined elsewhere. These were
there before the arm-stub.c file was added and didn't get moved when
it was. The get_dram_base() function is only used by arm/arm64, but
there is nothing architecture specific about it, which is why I put it
here to begin with. I don't feel strongly about this either way.
Thanks,
Roy
>
> --
> Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists