[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120605032221.GA32598@kroah.com>
Date: Mon, 4 Jun 2012 20:22:21 -0700
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: Ian Abbott <abbotti@....co.uk>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"fmhess@...rs.sourceforge.net" <fmhess@...rs.sourceforge.net>,
Ian Abbott <ian.abbott@....co.uk>,
Linux Kernel <linux-kernel@...r.kernel.org>,
H Hartley Sweeten <hartleys@...ionengravers.com>
Subject: Re: [PATCH] staging: comedi: ii_pci20kc: iobase and ioaddr are void
__iomem *
On Tue, May 22, 2012 at 11:15:12AM +0100, Ian Abbott wrote:
> On 2012-05-22 09:11, Dan Carpenter wrote:
> >On Mon, May 21, 2012 at 06:10:07PM -0700, H Hartley Sweeten wrote:
> >>@@ -210,7 +210,7 @@ static int pci20xxx_attach(struct comedi_device *dev,
> >> if (ret< 0)
> >> return ret;
> >>
> >>- devpriv->ioaddr = (void *)(unsigned long)it->options[0];
> >>+ devpriv->ioaddr = (void __iomem *)(unsigned long)it->options[0];
> >
> >
> >Obviously, your patch is fine, but I was wondering if it was a
> >problem that it->options was only a 32 bit? Seems like it would
> >deserve a comment.
>
> Yes, it's a bit of a strange driver, this one. It's a driver for a
> module sitting on a PCI card, but there is no driver I know of for
> the PCI card, and I've no idea what's actually ioremap'ing the
> memory!
>
> Maybe we should quietly drop it and see if anyone complains?
I'm all for deleting code :)
Send me a patch removing it and I'll be glad to apply it.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists