From: Christoph Hellwig <hch@infradead.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Christoph Hellwig <hch@infradead.org>,
James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.6: modular scsi/mca_53c9x doesn't work (fwd)
Date: Tue, 15 Jun 2004 08:17:19 +0100 [thread overview]
Message-ID: <20040615071719.GA12284@infradead.org> (raw)
In-Reply-To: <20040614225335.GP13951@fs.tum.de>
On Tue, Jun 15, 2004 at 12:53:36AM +0200, Adrian Bunk wrote:
> On Mon, Jun 14, 2004 at 08:22:15PM +0100, Christoph Hellwig wrote:
> > On Mon, Jun 14, 2004 at 08:52:56PM +0200, Adrian Bunk wrote:
> > > The issue described in the mail forwarded below is still present in
> > > 2.6.7-rc3-mm2 (but not specific to -mm).
> > >
> > > I'd suggest the following workaround:
> >
> > Please add the exports instead. It'll affect all the other 53C9X-based
> > drivers aswell.
>
> This sounds like a better solution.
>
> Patch below.
>
> cu
> Adrian
>
> --- linux-2.6.7-rc3-mm2-modular-no-smp/drivers/scsi/NCR53C9x.c.old 2004-06-15 00:44:36.000000000 +0200
> +++ linux-2.6.7-rc3-mm2-modular-no-smp/drivers/scsi/NCR53C9x.c 2004-06-15 00:47:23.000000000 +0200
> @@ -3646,4 +3646,15 @@
> }
> #endif
>
> +EXPORT_SYMBOL(esp_abort);
> +EXPORT_SYMBOL(esp_allocate);
> +EXPORT_SYMBOL(esp_deallocate);
> +EXPORT_SYMBOL(esp_initialize);
> +EXPORT_SYMBOL(esp_intr);
> +EXPORT_SYMBOL(esp_queue);
> +EXPORT_SYMBOL(esp_reset);
> +EXPORT_SYMBOL(esp_slave_alloc);
> +EXPORT_SYMBOL(esp_slave_destroy);
> +EXPORT_SYMBOL(esps_in_use);
> +
> MODULE_LICENSE("GPL");
Looks good to me, thanks.
prev parent reply other threads:[~2004-06-15 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 18:52 [patch] 2.6: modular scsi/mca_53c9x doesn't work (fwd) Adrian Bunk
2004-06-14 19:22 ` Christoph Hellwig
2004-06-14 22:53 ` Adrian Bunk
2004-06-15 7:17 ` Christoph Hellwig [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=20040615071719.GA12284@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=bunk@fs.tum.de \
--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