From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Michael Ang <mang@subcarrier.org>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] files still needing manual merging
Date: Wed, 9 Feb 2000 01:41:27 +0100 [thread overview]
Message-ID: <20000209014127.C2377@alpha.franken.de> (raw)
In-Reply-To: <Pine.BSF.4.10.10002081631440.11091-100000@cuzea.pair.com>; from Michael Ang on Tue, Feb 08, 2000 at 04:33:06PM -0500
On Tue, Feb 08, 2000 at 04:33:06PM -0500, Michael Ang wrote:
> `drivers/block/rd.c'
so far that's the only one in my tree, which is left. To get a kernel
compiled, I've just used the 2.3.42 version of that file (haven't commited
it yet). I can't say whether it works, because I'm now at the point, where
I get unresolved symbols:
ld: Unsatisfied symbols:
init_ext2_fs (code)
up_read (code)
uts_sem (data)
get_task_struct (code)
up_write (code)
pcibios_enable_device (code)
down_write (code)
down_read (code)
I've commited all the stuff, I've fixed to get it compiled. I'm going
to look into the problems with the unresolved symbols tomorrow, if
the issues are still unsolved.
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
next prev parent reply other threads:[~2000-02-09 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 21:33 [parisc-linux] files still needing manual merging Michael Ang
2000-02-09 0:39 ` Grant Grundler
2000-02-09 0:41 ` Thomas Bogendoerfer [this message]
2000-02-09 0:59 ` [parisc-linux] Merge status Michael Ang
2000-02-09 1:08 ` [parisc-linux] files still needing manual merging Grant Grundler
2000-02-09 1:19 ` Grant Grundler
2000-02-09 12:04 ` Thomas Bogendoerfer
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=20000209014127.C2377@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=mang@subcarrier.org \
--cc=parisc-linux@thepuffingroup.com \
/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