From: Vivek Mahajan <vmahajan@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: scsi_unregister_driver in 2.6.10
Date: Mon, 10 Jan 2005 17:57:32 -0700 [thread overview]
Message-ID: <e20f392505011016575aac92a1@mail.gmail.com> (raw)
I was working on my SCSI module and tried to use
scsi_unregister_driver(). But looks like it has been made GPL only. I
get unresolved symbol : driver_unregister(), when I tried to load the
module. I think it is #defined to driver_unregister() in
include/scsi/scsi_driver.h. And driver_unregister is exported as GPL
only.
At the same time, scsi_register_driver() works with non GPL code
without any problem. As this call is exclusively defined in
drivers/scsi/scsi_sysfs.c.
I was just wondering wss it unintentional Or there was a purpose
behind that to make scsi_register_driver( ) as non GPL and
scsi_unregister_driver( ) as GPL only.
Any help in this matter will be highly appreciated.
Regards,
Vivek
next reply other threads:[~2005-01-11 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 0:57 Vivek Mahajan [this message]
2005-01-11 3:00 ` scsi_unregister_driver in 2.6.10 Matthew Wilcox
2005-01-11 3:20 ` Vivek Mahajan
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=e20f392505011016575aac92a1@mail.gmail.com \
--to=vmahajan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox