From: Mike Snitzer <snitzer@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: James.Bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
Chandra Seetharaman <sekharan@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] [SCSI] scsi_dh: change scsi_dh_detach export to EXPORT_SYMBOL
Date: Sun, 22 Apr 2012 19:01:58 -0400 [thread overview]
Message-ID: <20120422230156.GA25181@redhat.com> (raw)
In-Reply-To: <20120422233454.7cdd0f35@pyramind.ukuu.org.uk>
Funny thing happens when you assume too much...
Anyway, your no compromises approach is admirable but it doesn't erase
the fact that all proprietary Linux drivers use EXPORT_SYMBOL code.
So what you're really saying is no proprietary drivers are allowed to be
loaded into a Linux kernel. Nice that you've made this scsi_dh_detach
change the frontline of a battle that has already been lost years ago.
Thanks for your time,
Mike
next prev parent reply other threads:[~2012-04-22 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 21:44 [RFC PATCH] scsi_dh: allow 3rd party multipath drivers to scsi_dh_detach Mike Snitzer
2011-12-20 7:31 ` Hannes Reinecke
2012-01-05 15:24 ` Mike Snitzer
2012-04-05 14:47 ` Mike Snitzer
2012-04-20 14:45 ` [RESEND][PATCH] [SCSI] scsi_dh: allow 3rd party multipath drivers to use scsi_dh_detach Mike Snitzer
2012-04-20 15:17 ` James Bottomley
2012-04-20 15:46 ` Mike Snitzer
2012-04-20 15:49 ` Chandra Seetharaman
2012-04-20 17:34 ` [PATCH v2] [SCSI] scsi_dh: change scsi_dh_detach export to EXPORT_SYMBOL Mike Snitzer
2012-04-20 20:41 ` Alan Cox
2012-04-20 21:58 ` Mike Snitzer
2012-04-20 22:20 ` Alan Cox
2012-04-20 22:58 ` Mike Snitzer
2012-04-20 23:14 ` Alan Cox
2012-04-20 23:34 ` Mike Snitzer
2012-04-22 22:13 ` Mike Snitzer
2012-04-22 22:34 ` Alan Cox
2012-04-22 23:01 ` Mike Snitzer [this message]
2012-04-22 23:13 ` Alan Cox
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=20120422230156.GA25181@redhat.com \
--to=snitzer@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sekharan@us.ibm.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 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).