From: David Woodhouse <dwmw2@infradead.org>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Patch: linux-2.5.2-pre8/drivers/mtd compilation fixes
Date: Sat, 05 Jan 2002 11:24:23 +0000 [thread overview]
Message-ID: <4082.1010229863@redhat.com> (raw)
In-Reply-To: <20020105025042.A23360@baldur.yggdrasil.com>
In-Reply-To: <20020105025042.A23360@baldur.yggdrasil.com>
adam@yggdrasil.com said:
> The following patch updates linux-2.5.2-pre8/drivers/mtd to compile.
> This entails some kdev_t fixes and other updates for changes to the
> block device driver interface.
Looks sane - thanks. I see no harm in sending it to Linus. Could you run
the blkmtd.c changes past spse@secret.org.uk first, though?
> In the case of one routine (ftl_reread_partitions), there was a goto
> to a nonexistant label (goto leave), so I think there may have been an
> incomplete patch applied to this subdirectory to begin with
Not in my tree - strange. Oh well, I'll deal with it when 2.5 stabilises
and I stop ignoring it.
> (also, drivers/mtd/bootldr.c refers to a nonexistant "struct tag", but that
> file is apparently not currently compiled anyhow).
Currently, it's only compiled in the iPAQ kernel tree, where it works - I'm
waiting for the iPAQ people and Russell to stop arguing about how it should
be done, so the result will work in the proper ARM tree (and hence Linus'
tree) too.
Btw, where did you get the address 'mtd@infradead.org' from? The list moved
a while ago, and I was going to remove the forwarding some time soon.
--
dwmw2
next prev parent reply other threads:[~2002-01-05 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 10:50 Patch: linux-2.5.2-pre8/drivers/mtd compilation fixes Adam J. Richter
2002-01-05 11:24 ` David Woodhouse [this message]
2002-01-05 12:42 ` Russell King
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=4082.1010229863@redhat.com \
--to=dwmw2@infradead.org \
--cc=adam@yggdrasil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox