From: Matthew Wilcox <matthew@wil.cx>
To: Vivek Mahajan <vmahajan@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi_unregister_driver in 2.6.10
Date: Tue, 11 Jan 2005 03:00:07 +0000 [thread overview]
Message-ID: <20050111030007.GS27371@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <e20f392505011016575aac92a1@mail.gmail.com>
On Mon, Jan 10, 2005 at 05:57:32PM -0700, Vivek Mahajan wrote:
> 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.
I think this was unintentional. However, I'm not sure there's a
compelling reason to undo it -- scsi_register_driver is for registering
top-level drivers like st, sr, sd and osst. What kind of driver is this
that you're writing?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-01-11 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 0:57 scsi_unregister_driver in 2.6.10 Vivek Mahajan
2005-01-11 3:00 ` Matthew Wilcox [this message]
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=20050111030007.GS27371@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=linux-scsi@vger.kernel.org \
--cc=vmahajan@gmail.com \
/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.