mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: dwmw2@infradead.org, bernds_cb1@t-online.de
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH 4/4] MTD: Fix a bad dependency in the Blackfin code
Date: Thu, 12 Feb 2009 10:40:15 +0000	[thread overview]
Message-ID: <20090212104015.26766.41302.stgit@warthog.procyon.org.uk> (raw)
In-Reply-To: <20090212104000.26766.11068.stgit@warthog.procyon.org.uk>

From: Bernd Schmidt <bernd.schmidt@analog.com>

Fix a bad dependency in the Blackfin code on a RomFS config symbol that doesn't
exist upstream.

Signed-off-by: Bernd Schmidt <bernd.schmidt@analog.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Tested-by: Bernd Schmidt <bernd.schmidt@analog.com>
---

 arch/blackfin/kernel/process.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/arch/blackfin/kernel/process.c b/arch/blackfin/kernel/process.c
index 33e2e89..7f7ce07 100644
--- a/arch/blackfin/kernel/process.c
+++ b/arch/blackfin/kernel/process.c
@@ -337,7 +337,7 @@ int _access_ok(unsigned long addr, unsigned long size)
 	if (addr >= memory_mtd_end && (addr + size) <= physical_mem_end)
 		return 1;
 
-#ifdef CONFIG_ROMFS_MTD_FS
+#ifdef CONFIG_ROMFS_ON_MTD
 	/* For XIP, allow user space to use pointers within the ROMFS.  */
 	if (addr >= memory_mtd_start && (addr + size) <= memory_mtd_end)
 		return 1;


      parent reply	other threads:[~2009-02-12 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 10:40 [PATCH 1/4] NOMMU: Present backing device capabilities for MTD chardevs David Howells
2009-02-12 10:40 ` [PATCH 2/4] NOMMU: Add support for direct mapping through mtdconcat if possible David Howells
2009-02-12 10:40 ` [PATCH 3/4] NOMMU: Make it possible for RomFS to use MTD devices directly David Howells
2009-02-20  0:12   ` Andrew Morton
2009-02-20 12:11   ` David Howells
2009-02-20 12:31   ` David Howells
2009-02-12 10:40 ` David Howells [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=20090212104015.26766.41302.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=bernds_cb1@t-online.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®