From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: Andre Hedrick <andre@linux-ide.org>,
axboe@suse.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Patch: linux-2.5.41/drivers/ide - build IDE as a module
Date: 10 Oct 2002 15:18:36 +0100 [thread overview]
Message-ID: <1034259516.6463.10.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20021010064457.A460@baldur.yggdrasil.com>
On Thu, 2002-10-10 at 14:44, Adam J. Richter wrote:
> 1. For the time being, I have reassembled some of the
> drivers/ide object files into ide-mod.o again, because there are some
> circular references (not necessarily a bad thing) that modprobe cannot
> otherwise handle. For now, this includes putting ide-probe in
> ide-mod.
I don't think that is actually avoidable. We end up with a lump that I'd
probably call "ide-core" which is fine.
> 2. I have changed cmd640.o and legacy.o from dep_bool to
> dep_tristate and made them also depend on $CONFIG_BLK_DEV_IDE, so
> that they will only be offered as modules if ide-mod.o is a
> module (since, like any IDE driver, they require some symbols in
> ide-mod.o).
Sounds right
> These changes are probably not perfect, but I think they
> should be an improvement with no real disadvantages in comparison to
> what they replace, so I would encourage you to integrate the changes
> if you see no problem. Please let me know what you want to do, or if
> there is something more you'd like me to do regarding this patch.
I'll go over it again, but I have no major problem with applying them
and working from there to clean up the corners. Firstly however do one
little thing - dont put extern blah() in the code, add them to the right
header files.
next prev parent reply other threads:[~2002-10-10 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 13:44 Adam J. Richter
2002-10-10 14:18 ` Alan Cox [this message]
2002-10-10 14:26 ` Adam J. Richter
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=1034259516.6463.10.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=adam@yggdrasil.com \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®