From: "Ian" <Relativity@HumanHeuristic.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: mtd@infradead.org
Subject: Re: inter-module-2.2.17 patch
Date: Thu, 30 Nov 2000 23:25:26 +1000 [thread overview]
Message-ID: <200011301325.XAA32592@singularity.tronunltd.com> (raw)
I've just downloaded it ... lemme build it up and give it a go .. back shortly.
----- Original Message -----
>From: "David Woodhouse" <dwmw2@infradead.org>
>To: <mark.langsdorf@amd.com>
>Subject: Re: inter-module-2.2.17 patch
>Date: Thu, 30 Nov 2000 12:08:31 +0000
>
>
> mark.langsdorf@amd.com said:
> > What should I be doing to get the latest MTD code to compile against
> > 2.2.17?
>
> OK, I've just put a complete patch for the inter_module_xxx stuff along
> with the latest CVS code into CVS.
>
> It's patches/mtd-patch-2.2.17-20001130
>
> I've compiled in the DiskOnChip 2000 driver, dug a doc2000 eval board out
> of a drawer and booted it. It finds the device and complains a lot about
> bad ECC, but that's not very surprising because it was my Grub test device
> and probably doesn't have a valid NFTL on it.
>
>
> --
> dwmw2
>
>
>
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
>
--
http://HumanHeuristic.com/
"Bringing people together in a world full of computers"
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-11-30 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 13:25 Ian [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-30 16:53 inter-module-2.2.17 patch mark.langsdorf
2000-11-30 17:01 ` David Woodhouse
2000-11-30 14:42 mark.langsdorf
2000-11-30 14:04 Ian
2000-11-30 15:32 ` David Woodhouse
2000-11-30 16:47 ` David Woodhouse
2000-11-30 13:47 Ian
2000-11-30 13:44 Ian
2000-11-30 13:45 ` David Woodhouse
2000-11-29 20:23 mark.langsdorf
2000-11-30 9:34 ` David Woodhouse
2000-11-30 12:08 ` 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=200011301325.XAA32592@singularity.tronunltd.com \
--to=relativity@humanheuristic.com \
--cc=dwmw2@infradead.org \
--cc=mtd@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.