All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@cotw.com>
To: "Adam J. Richter" <adam@ns1.yggdrasil.com>
Cc: dwmw2@redhat.com, linux-kernel@vger.kernel.org,
	linux-mtd@lists.infradead.org
Subject: Re: linux-2.4.6-pre8/drivers/mtd/nand/spia.c: undefined symbols
Date: Tue, 03 Jul 2001 10:35:03 -0500	[thread overview]
Message-ID: <3B41E627.9A0688AA@cotw.com> (raw)
In-Reply-To: 200107031310.GAA03900@ns1.yggdrasil.com

"Adam J. Richter" wrote:
> 
>         If there is no architecture on which
> linux-2.4.6-pre8/drivers/mtd/nand/spia.c will compile in its
> "pristine" form, then the CONFIG_MTD_NAND_SPIA should be commented
> out from drivers/mtd/nand/Config.in to avoid wasting the time of
> users and automated build processes alike that just want to build
> all available modules by default.  (At the moment, this code is
> not even bracketed by CONFIG_EXPERIMENTAL, although changing that
> would not be a sufficient fix.)
> 
David has fixed this and it is in the MTD CVS now.

>         Alternatively, if you will send me a one line description
> of each of those four #define parameters, I will be happy to do the grunt
> work of submiting a patch to you or whoever is appropriate to replace
> those values with module and setup parameters that default to those
> values if there are #defined and otherwise will abort initialization
> if they are not #defined and no values were provided at run time.
> (Or, better, yet, you can do this work!)
> 
I have filled in the #define values and placed the new 'spia.c' into
the MTD CVS. I added comments for how those various values should be
defined. Shame on me for forgetting to comment those months ago. Sorry.
I believe that fixes things now?

-Steve

-- 
 Steven J. Hill - Embedded SW Engineer

  reply	other threads:[~2001-07-03 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 13:10 linux-2.4.6-pre8/drivers/mtd/nand/spia.c: undefined symbols Adam J. Richter
2001-07-03 15:35 ` Steven J. Hill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-03 15:53 Adam J. Richter
2001-07-01 22:07 Adam J. Richter
2001-07-02 12:38 ` Steven J. Hill
2001-07-02 12:52   ` Alan Cox
2001-07-02 13:14     ` David Woodhouse
2001-07-02 13:14       ` David Woodhouse
2001-07-03 17:57     ` Steven J. Hill
2001-07-02 12:53   ` David Woodhouse
2001-07-02 12:53     ` 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=3B41E627.9A0688AA@cotw.com \
    --to=sjhill@cotw.com \
    --cc=adam@ns1.yggdrasil.com \
    --cc=dwmw2@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.