Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Florian Fainelli <florian@openwrt.org>
Cc: linux-mips@linux-mips.org, David Daney <ddaney@caviumnetworks.com>
Subject: Re: [PATCH 1/2] octeon: flash_setup blows on !MTD_COMPLEX_MAPPINGS and !MTD_MAP_BANK_WIDTH_1
Date: Mon, 22 Jun 2009 15:31:19 +0100	[thread overview]
Message-ID: <20090622143119.GB25289@linux-mips.org> (raw)
In-Reply-To: <200906221115.23628.florian@openwrt.org>

On Mon, Jun 22, 2009 at 11:15:23AM +0200, Florian Fainelli wrote:

> diff --git a/arch/mips/cavium-octeon/flash_setup.c b/arch/mips/cavium-octeon/flash_setup.c
> index 008f657..894edbb 100644
> --- a/arch/mips/cavium-octeon/flash_setup.c
> +++ b/arch/mips/cavium-octeon/flash_setup.c
> @@ -41,6 +41,7 @@ static int __init flash_init(void)
>  	 */
>  	union cvmx_mio_boot_reg_cfgx region_cfg;
>  	region_cfg.u64 = cvmx_read_csr(CVMX_MIO_BOOT_REG_CFGX(0));
> +#if defined (CONFIG_MTD_COMPLEX_MAPPINGS) && (CONFIG_MTD_MAP_BANK_WIDTH_1)
              ^
              no space
                                                ^^^
                                  This should be defined(CONFIG_MTD_...)

Or bad things may happen.

The parenthesis in this expression are unnecessary.

>  	if (region_cfg.s.en) {
>  		/*
>  		 * The bootloader always takes the flash and sets its
> @@ -78,6 +79,7 @@ static int __init flash_init(void)
>  			pr_err("Failed to register MTD device for flash\n");
>  		}
>  	}
> +#endif /* (CONFIG_MTD_COMPLEX_MAPPINGS) && (CONFIG_MTD_MAP_BANK_WIDTH_1) */
>  	return 0;
>  }

  Ralf

      reply	other threads:[~2009-06-22 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22  9:15 [PATCH 1/2] octeon: flash_setup blows on !MTD_COMPLEX_MAPPINGS and !MTD_MAP_BANK_WIDTH_1 Florian Fainelli
2009-06-22 14:31 ` Ralf Baechle [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=20090622143119.GB25289@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    /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