From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide <linux-ide@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexis Bruemmer <alexisb@us.ibm.com>,
Mike Anderson <andmike@us.ibm.com>
Subject: Re: [PATCH v3] libsas: move ATA bits into a separate module
Date: Mon, 18 Sep 2006 20:00:33 +0100 [thread overview]
Message-ID: <20060918190033.GD17670@infradead.org> (raw)
In-Reply-To: <4509DA77.7000508@us.ibm.com>
On Thu, Sep 14, 2006 at 03:40:55PM -0700, Darrick J. Wong wrote:
> Jeff Garzik wrote:
>
> > I disagree completely with this approach.
> >
> > You don't need a table of hooks for the case where libata is disabled in
> > .config. Thus, it's only useful for the case where libsas is loaded as
> > a module, but libata is not.
>
> Indeed, I misunderstood what James Bottomley wanted, so I reworked the
> patch. It has the same functionality as before, but this module uses
> the module loader/symbol resolver for all the functions in libata, and
> allows libsas to (optionally) call into sas_ata with weak references by
> pushing a table of the necessary function pointers into libsas at
> sas_ata load time. Thus, libsas doesn't need to load libata/sas_ata
> unless it actually finds a SATA device.
NACK again. Week references are bad. Please change it back to normal
hard references so that it works like everything else in the kernel.
next prev parent reply other threads:[~2006-09-18 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4508A0A2.2080605@us.ibm.com>
[not found] ` <450971D3.2040405@garzik.org>
2006-09-14 22:40 ` [PATCH v3] libsas: move ATA bits into a separate module Darrick J. Wong
2006-09-14 22:49 ` Jeff Garzik
2006-09-18 19:00 ` Christoph Hellwig [this message]
2006-09-18 21:47 ` Jeff Garzik
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=20060918190033.GD17670@infradead.org \
--to=hch@infradead.org \
--cc=alexisb@us.ibm.com \
--cc=andmike@us.ibm.com \
--cc=djwong@us.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).