public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Meelis Roos <mroos@linux.ee>,
	linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: 2.5.17: ide & ext2 unresolved symbols in modules
Date: Tue, 21 May 2002 21:00:42 +0200	[thread overview]
Message-ID: <3CEA995A.50007@evision-ventures.com> (raw)
In-Reply-To: <Pine.GSO.4.43.0205212200500.19324-100000@romulus.cs.ut.ee> <3CEA9C42.B2871594@zip.com.au>

Uz.ytkownik Andrew Morton napisa?:
> Meelis Roos wrote:
> 
>>depmod: *** Unresolved symbols in /lib/modules/2.5.17/kernel/drivers/ide/ide-disk.o
>>depmod:         udma_tcq_enable
> 
> 
> Not sure.

Fixed in IDE 65. It was indeed missing. (Modulo the fact that udma_tcq_enable
and udma_enable should be merged.)


> 
> 
>>depmod: *** Unresolved symbols in /lib/modules/2.5.17/kernel/drivers/ide/ide-mod.o
>>depmod:         blk_get_request
> 
> 
> Needs exporting.  I'll let Jens do that...
> 
> 
>>depmod: *** Unresolved symbols in /lib/modules/2.5.17/kernel/fs/ext2/ext2.o
>>depmod:         write_mapping_buffers
> 
> 
> Needs to be exported.  I'll fix that.
> 
> Thanks.
> 
> -
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 



-- 
- phone: +49 214 8656 283
- job:   eVision-Ventures AG, LEV .de (MY OPINIONS ARE MY OWN!)
- langs: de_DE.ISO8859-1, en_US, pl_PL.ISO8859-2, last ressort: ru_RU.KOI8-R


      reply	other threads:[~2002-05-21 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 19:03 2.5.17: ide & ext2 unresolved symbols in modules Meelis Roos
2002-05-21 19:13 ` Andrew Morton
2002-05-21 19:00   ` Martin Dalecki [this message]

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=3CEA995A.50007@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=akpm@zip.com.au \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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