From: James Bottomley <James.Bottomley@steeleye.com>
To: Eric Kerin <eric@bootseg.com>
Cc: "Larry W. Finger" <Larry.Finger@lwfinger.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Kernel oops in 2.6.1 when loading aha152x_cs.ko
Date: 10 Jan 2004 15:43:56 -0500 [thread overview]
Message-ID: <1073767436.1945.60.camel@mulgrave> (raw)
In-Reply-To: <1073761884.6434.12.camel@opiate>
On Sat, 2004-01-10 at 14:11, Eric Kerin wrote:
> Yes, I agree the best place to put that block of code would have been
> aha152x_stub.c, but I couldn't find an existing way to reference the
> driver template from that file. The "s" struct is a aha152x_setup, not a
> aha152x_driver_template. That's why I put it in aha152x.c with an ifdef
>
> I could setup aha152x_driver_template as an extern, but since I'm still
> somewhat new around here, wasn't sure if that was a good way to handle
> it. If an extern is fine with you, I'll code it up that way. Although
> in that case, it would be best to put the INIT_LIST_HEAD in module_init.
> That's where it would normally be done, and we would have a reference at
> that point.
Yes, I see the problem, that's what I get for suggesting something
without trying it.
However, could you try Juergen Fischer's patch, please...that's really
done the way I wanted.
James
prev parent reply other threads:[~2004-01-10 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 20:14 Kernel oops in 2.6.1 when loading aha152x_cs.ko Larry W. Finger
2004-01-10 1:37 ` Eric Kerin
2004-01-10 5:27 ` Larry W. Finger
2004-01-10 6:38 ` Eric Kerin
2004-01-10 15:03 ` James Bottomley
2004-01-10 17:09 ` Larry W. Finger
2004-01-10 17:35 ` Juergen E. Fischer
2004-01-10 19:11 ` Eric Kerin
2004-01-10 20:43 ` James Bottomley [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=1073767436.1945.60.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Larry.Finger@lwfinger.net \
--cc=eric@bootseg.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.