Hi,
On Thu, Jan 19, 2017 at 02:24:24PM +, Russell King - ARM Linux wrote:
> On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> > +#define VECTORS_BASE 0x
>
> This should be UL(0x)
This has been taken care in v2.
Regards
afzal
Hi,
On Thu, Jan 19, 2017 at 02:24:24PM +, Russell King - ARM Linux wrote:
> On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> > +#define VECTORS_BASE 0x
>
> This should be UL(0x)
This has been taken care in v2.
Regards
afzal
Hi,
On Thu, Jan 19, 2017 at 02:24:24PM +, Russell King - ARM Linux wrote:
> On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> > +++ b/arch/arm/include/asm/memory.h
> > +#define VECTORS_BASE 0x
>
> This should be UL(0x)
> > -
Hi,
On Thu, Jan 19, 2017 at 02:24:24PM +, Russell King - ARM Linux wrote:
> On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> > +++ b/arch/arm/include/asm/memory.h
> > +#define VECTORS_BASE 0x
>
> This should be UL(0x)
> > -
On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> diff --git a/arch/arm/include/asm/memory.h b/arch/arm/include/asm/memory.h
> index 76cbd9c674df..9cc9f1dbc88e 100644
> --- a/arch/arm/include/asm/memory.h
> +++ b/arch/arm/include/asm/memory.h
> @@ -83,6 +83,8 @@
> #define
On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> diff --git a/arch/arm/include/asm/memory.h b/arch/arm/include/asm/memory.h
> index 76cbd9c674df..9cc9f1dbc88e 100644
> --- a/arch/arm/include/asm/memory.h
> +++ b/arch/arm/include/asm/memory.h
> @@ -83,6 +83,8 @@
> #define
Hi afzal,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc4 next-20170119]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi afzal,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc4 next-20170119]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
+ Marvell Berlin SoC maintainers - Sebastian, Jisheng
On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> For MMU configurations, VECTORS_BASE is always 0x, a macro
> definition will suffice.
>
> Once exception address is handled dynamically for no-MMU also (this
> would
+ Marvell Berlin SoC maintainers - Sebastian, Jisheng
On Thu, Jan 19, 2017 at 02:07:39AM +0530, afzal mohammed wrote:
> For MMU configurations, VECTORS_BASE is always 0x, a macro
> definition will suffice.
>
> Once exception address is handled dynamically for no-MMU also (this
> would
For MMU configurations, VECTORS_BASE is always 0x, a macro
definition will suffice.
Once exception address is handled dynamically for no-MMU also (this
would involve taking care of region setup too), VECTORS_BASE can be
removed from Kconfig.
Suggested-by: Russell King
For MMU configurations, VECTORS_BASE is always 0x, a macro
definition will suffice.
Once exception address is handled dynamically for no-MMU also (this
would involve taking care of region setup too), VECTORS_BASE can be
removed from Kconfig.
Suggested-by: Russell King
Signed-off-by:
12 matches
Mail list logo