public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: llandre <r&d@wawnet.biz>
Cc: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Help to understand error messages (MTD on Samsung NAND chips)
Date: Wed, 16 Jul 2003 23:34:23 +0100	[thread overview]
Message-ID: <1058394863.2914.30.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <5.1.1.6.0.20030716101901.026acca0@192.168.2.1>

On Wed, 2003-07-16 at 09:51, llandre wrote:
> thanks for your quick response. I downloaded and applied the latest 
> snapshot (2003-07-15) but, after that, I can't build my own low-level 
> driver, derived it from Marius Gröger's edb7312.c, anymore :-(

I changed a lot of stuff in the nand drivers. In drivers/mtd/nand, run
the command: cvs diff -up -D "last month" edb7312.c

> I have a very strange error about the __init end __exit keywords?!?!

#include <linux/init.h>

> Besides, I had a look at the new MTD's sources and I saw that some 
> functions changed the formal parameteres (for example nand_scan).

Add the extra 'struct mtd_info *' argument to your own methods; you can
ignore it if you want. Pass '1' as the second argument to nand_scan()
since you only have one chip there.

-- 
dwmw2

  reply	other threads:[~2003-07-16 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 16:39 Help to understand error messages (MTD on Samsung NAND chips) llandre
2003-07-15 17:45 ` Thomas Gleixner
2003-07-16  8:51   ` llandre
2003-07-16 22:34     ` David Woodhouse [this message]
2003-07-31 16:16   ` llandre
2003-07-31 18:56     ` Thomas Gleixner

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=1058394863.2914.30.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=r&d@wawnet.biz \
    --cc=tglx@linutronix.de \
    /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