public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hildner <christian.hildner@hob.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Mark Maule <maule@sgi.com>, Christoph Hellwig <hch@infradead.org>,
	akpm@osdl.org, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] altix:  export sn_pcidev_info_get
Date: Tue, 21 Feb 2006 09:20:57 +0100	[thread overview]
Message-ID: <43FACD69.4020602@hob.de> (raw)
In-Reply-To: 1140508994.3082.16.camel@laptopd505.fenrus.org

Arjan van de Ven schrieb:

>On Mon, 2006-02-20 at 20:47 -0600, Mark Maule wrote:
>  
>
>>On Mon, Feb 20, 2006 at 08:17:14PM +0000, Christoph Hellwig wrote:
>>    
>>
>>>On Tue, Feb 14, 2006 at 10:23:37AM -0600, Mark Maule wrote:
>>>      
>>>
>>>>Export sn_pcidev_info_get.
>>>>        
>>>>
>>>Tony or Andrew please back this out again.  The only reason SGI wants this is
>>>to support their illegal graphics driver, and no core code uses it.
>>>
>>>And Mark, please stop submitting such patches.
>>>      
>>>
>>All I'm doing by exporting sn_pcidev_info_get is allowing a module to use
>>the SGI SN_PCIDEV_BUSSOFT() macro which will tell a driver which piece of
>>altix PCI hw its device is sitting behind (e.g. PCIIO_ASIC_TYPE_TIOCP et. al).
>>
>>While I acknowledge that the gfx driver folks requested this, I don't
>>understand what is "illegal" about this export, or the driver which wants
>>to use it.  What am I missing here?
>>    
>>
>
>so you would have no objection to making this a _GPL export ?
>
Hi Folks,

sn_* symbols are "their" symbols so I can't see any legitimation for 
anyone else to not let them export their symbols as they want. They are 
doing a great job on linux to make it run scalable on the biggest 
machines on earth. Or don't you like the idea of running Linux on those 
supercomputers?

Christian



  reply	other threads:[~2006-02-21  8:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060214162337.GA16954@sgi.com>
2006-02-20 20:17 ` [PATCH] altix: export sn_pcidev_info_get Christoph Hellwig
2006-02-20 21:39   ` Andrew Morton
2006-02-21 10:48     ` Christoph Hellwig
2006-02-25 11:55       ` Christoph Hellwig
2006-02-21  2:47   ` Mark Maule
2006-02-21  8:03     ` Arjan van de Ven
2006-02-21  8:20       ` Christian Hildner [this message]
2006-02-21 10:36     ` Christoph Hellwig
2006-02-21 11:23       ` Jes Sorensen
2006-02-25 11:55         ` Christoph Hellwig
2006-03-01 13:34           ` Jes Sorensen
2006-03-01 14:41 Luck, Tony

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=43FACD69.4020602@hob.de \
    --to=christian.hildner@hob.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maule@sgi.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