public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Brian J. Murrell" <e88cd5ffd87e620fdc30b3e6db510d03@interlinx.bc.ca>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD Config.in items not escaped by bus availability
Date: Thu, 07 Nov 2002 14:00:34 +0000	[thread overview]
Message-ID: <7374.1036677634@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20021107135052.GA13914@pc.ilinx>

e88cd5ffd87e620fdc30b3e6db510d03@interlinx.bc.ca said:
>  I hope I am understanding the question/scenario you are proposing,
> but the answer seems to simple, so I am sure I am missing something.

> When/if someone makes that UML mapping driver, it would have it's

<PEDANT>
	YM "its"
</PEDANT>

(Sorry, customers being bloody stupid at me today and I have to be nasty to 
_someone_ or my brain will explode :)

> CONFIG_MTD_UML (or whatever they will call it) outside of the
> CONFIG_MEMORY bus protected portions of the MTD Config.in files.

But the options for the _chips_ it's able to find in that mapping are 
disabled because CONFIG_MEMORY_BUS is turned off.

A better plan would be to allow the chip configuration to be enabled iff 
there is at least one mapping driver enabled. 

--
dwmw2

  reply	other threads:[~2002-11-07 13:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 16:22 MTD Config.in items not escaped by bus availability Hicks, Jamey
2002-10-30 17:30 ` Brian J. Murrell
     [not found] ` <20021030185507.GA31547@wohnheim.fh-wedel.de>
2002-10-30 19:38   ` Brian J. Murrell
     [not found]     ` <20021030201608.GA28523@wohnheim.fh-wedel.de>
2002-10-30 20:49       ` Brian J. Murrell
     [not found]         ` <20021030214341.GC25383@wohnheim.fh-wedel.de>
2002-10-30 22:46           ` Brian J. Murrell
2002-10-31 16:53             ` Jörn Engel
2002-10-31 18:37               ` Jörn Engel
2002-10-31 19:05                 ` Brian J. Murrell
2002-10-31 21:00                   ` Jörn Engel
2002-11-03 11:59                 ` Brian J. Murrell
2002-11-04 14:17                   ` Jörn Engel
2002-11-04 14:29                     ` Brian J. Murrell
2002-11-04 17:13                       ` Jörn Engel
2002-11-06 20:45                         ` Brian J. Murrell
2002-11-07  8:00                           ` David Woodhouse
2002-11-07 13:50                             ` Brian J. Murrell
2002-11-07 14:00                               ` David Woodhouse [this message]
2002-11-07 15:33                                 ` Jörn Engel
2002-11-07 15:34                                   ` David Woodhouse
2002-11-07 15:54                                     ` Jörn Engel
2002-11-07 15:58                                       ` David Woodhouse
2002-11-07 16:00                                         ` Jörn Engel
2002-11-07 15:21                               ` Jörn Engel
2002-11-07 12:13                         ` Unable to handle kernel NULL pointer dereference at virtual address 0000000c nur
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30 22:09 MTD Config.in items not escaped by bus availability Hicks, Jamey
2002-10-28 13:48 Brian J. Murrell

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=7374.1036677634@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=e88cd5ffd87e620fdc30b3e6db510d03@interlinx.bc.ca \
    --cc=linux-mtd@lists.infradead.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