From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Tue, 29 Mar 2016 12:22:44 -0700
Subject: Did PCI/IRQ allocation change significantly after 4.2 kernel?
In-Reply-To: <20160329191840.GA30945@kroah.com>
References: <BN1PR04MB551EAC58AE54505BC4F48CCA6870@BN1PR04MB551.namprd04.prod.outlook.com>
	<20160329144244.GA24067@kroah.com>
	<20160329144314.GA24237@kroah.com>
	<1459265269.2010.7.camel@rtd-VirtualBox>
	<20160329154353.GA26108@kroah.com>
	<1459276021.2010.19.camel@rtd-VirtualBox>
	<20160329183851.GA9186@kroah.com>
	<1459278706.2010.24.camel@rtd-VirtualBox>
	<20160329191840.GA30945@kroah.com>
Message-ID: <20160329192244.GA31666@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Tue, Mar 29, 2016 at 12:18:40PM -0700, Greg KH wrote:
> > That is encouraging and persuasive.  I will make submitting the driver
> > one of my pet projects.  I need to put a new coat of paint on it before
> > I submit it for consideration, though.  Do I post to this mailing list
> > when I'm ready?  Or is there a more pertinent one?
> 
> I can take it "as-is" through the staging tree (drivers/staging/) which
> lets the community start to clean it up now, if you don't have the
> time to do the work now.  Then you can work within the kernel
> development process to polish up the remaining issues before we merge it
> out of the staging tree into the "real" portion of the kernel.
> 
> If you are interested in this, just let me know.

In looking at your driver closer, what exactly is it doing?  At first
glance, it seems to be just a bunch of ioctls to directly access the
memory in the card, is that correct?  If so, why not just use the UIO
layer instead?  If not, what is the driver trying to do?

thanks,

greg k-h