public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Sébastien Côté" <scote1@Matrox.COM>
To: David Woodhouse <dwmw2@infradead.org>
Cc: MTD Mailing List <mtd@infradead.org>,
	Michael Elizabeth Chastain <mec@shout.net>,
	David Weinehall <tao@acc.umu.se>
Subject: Re: Config.in
Date: Thu, 13 Jul 2000 09:58:24 -0400	[thread overview]
Message-ID: <396DCB00.D5F26E57@matrox.com> (raw)
In-Reply-To: 17260.963495837@cygnus.co.uk

David Woodhouse wrote:
> 
> Hmmm. Talk to David and Michael.
> 
> scote1@matrox.com said:
> > Running make xconfig on 2.2.15, I get the following
> > drivers/mtd/Config.in: 14: unknown command
> 
> > However, make menuconfig doesn't generate any error.  I'm not a kernel
> > config specialist so I don't know if define_tristate was introduced in
> > 2.3 or why in doesn't work only with xconfig, but this is definitly a
> > bug of some sort.

Another thing I just noticed is that the links in linux/modules are
wrong for MTD.  They point to linux/Lost/mtd*.  But the link for jffs.o
is correct! I didn't notice this before because I linked all my JFFS and
MTD stuff directly in /lib/modules/...  I didn't use the patch to
install MTD so maybe I did something wrong but where does the kernel
look to make these links ?

-- 
Sébastien Côté


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-07-13 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-11 21:23 mtd devices & jffs Juan Gonzo
2000-07-12  8:19 ` David Woodhouse
2000-07-12  9:35   ` David Woodhouse
2000-07-13 12:53     ` Config.in Sébastien Côté
2000-07-13 13:43       ` Config.in David Woodhouse
2000-07-13 13:58         ` Sébastien Côté [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-14  3:58 Config.in Michael Elizabeth Chastain
2000-07-14  7:30 ` Config.in David Woodhouse

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=396DCB00.D5F26E57@matrox.com \
    --to=scote1@matrox.com \
    --cc=dwmw2@infradead.org \
    --cc=mec@shout.net \
    --cc=mtd@infradead.org \
    --cc=tao@acc.umu.se \
    /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