From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] microblaze: remove wrong define CONFIG_SYS_FLASH_PROTECTION
Date: Wed, 27 Jun 2012 10:32:00 +0200 [thread overview]
Message-ID: <4FEAC500.60601@monstr.eu> (raw)
In-Reply-To: <1340749706-27266-1-git-send-email-linz@li-pro.net>
On 06/27/2012 12:28 AM, Stephan Linz wrote:
> CONFIG_SYS_FLASH_PROTECTION will defined twice. The second one
> is outside the flash configuration context and we can remove
> it safely.
>
> Signed-off-by: Stephan Linz<linz@li-pro.net>
> ---
> include/configs/microblaze-generic.h | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/include/configs/microblaze-generic.h b/include/configs/microblaze-generic.h
> index 295d123..5f16820 100644
> --- a/include/configs/microblaze-generic.h
> +++ b/include/configs/microblaze-generic.h
> @@ -200,8 +200,6 @@
> # define CONFIG_ENV_IS_NOWHERE 1
> # define CONFIG_ENV_SIZE 0x1000
> # define CONFIG_ENV_ADDR (CONFIG_SYS_MONITOR_BASE - CONFIG_ENV_SIZE)
> -/* hardware flash protection */
> -# define CONFIG_SYS_FLASH_PROTECTION
> #endif /* !FLASH */
>
> /* system ace */
Applied all three patches to microblaze custodian repo with minor cleanup.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2012-06-27 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 22:28 [U-Boot] [PATCH 1/3] microblaze: remove wrong define CONFIG_SYS_FLASH_PROTECTION Stephan Linz
2012-06-26 22:28 ` [U-Boot] [PATCH 2/3] microblaze: avoid compile error on systems without cfi flash Stephan Linz
2012-06-26 22:28 ` [U-Boot] [PATCH 3/3] microblaze: Enable ubi support Stephan Linz
2012-06-27 8:32 ` Michal Simek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FEAC500.60601@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox