[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa686aa40805041424x26de27a1g16959e7b9c7ddbf2@mail.gmail.com>
Date: Sun, 4 May 2008 15:24:25 -0600
From: "Grant Likely" <grant.likely@...retlab.ca>
To: monstr@...nam.cz
Cc: linux-kernel@...r.kernel.org, arnd@...db.de,
linux-arch@...r.kernel.org, stephen.neuendorffer@...inx.com,
John.Linn@...inx.com, john.williams@...alogix.com, matthew@....cx,
will.newton@...il.com, drepper@...hat.com,
microblaze-uclinux@...e.uq.edu.au,
"Michal Simek" <monstr@...str.eu>
Subject: Re: [PATCH 01/56] microblaze_v2: Kconfig patches
On Sun, May 4, 2008 at 5:40 AM, <monstr@...nam.cz> wrote:
> From: Michal Simek <monstr@...str.eu>
>
>
> Signed-off-by: Michal Simek <monstr@...str.eu>
> diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig
> new file mode 100644
> index 0000000..49767d1
> --- /dev/null
> +++ b/arch/microblaze/Kconfig
<snip>
> +config XILINX_UNCACHED_SHADOW
> + bool "Are you using uncached shadow for RAM ?"
> + depends on MICROBLAZE
Isn't CONFIG_MICROBLAZE a given?
> diff --git a/arch/microblaze/platform/Kconfig.platform b/arch/microblaze/platform/Kconfig.platform
> new file mode 100644
> index 0000000..64cbb80
> --- /dev/null
> +++ b/arch/microblaze/platform/Kconfig.platform
<snip>
> +config HACK
> + bool "Increase performance"
> + default y
Is this appropriate for mainline? If so, it should have a better
description. :-)
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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