[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201201302004.33083.arnd@arndb.de>
Date: Mon, 30 Jan 2012 20:04:32 +0000
From: Arnd Bergmann <arnd@...db.de>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Kevin Cernekee <cernekee@...il.com>,
Ralf Baechle <ralf@...ux-mips.org>,
Paul Mundt <lethal@...ux-sh.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Myron Stowe <myron.stowe@...hat.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Lucas De Marchi <lucas.demarchi@...fusion.mobi>,
Dmitry Kasatkin <dmitry.kasatkin@...el.com>,
James Morris <jmorris@...ei.org>,
"John W. Linville" <linville@...driver.com>,
Michael Witten <mfwitten@...il.com>, linux-mips@...ux-mips.org,
linux-kernel@...r.kernel.org, linux-sh@...r.kernel.org,
linux-arch@...r.kernel.org
Subject: Re: [PATCH 1/3] lib: add NO_GENERIC_PCI_IOPORT_MAP
On Monday 30 January 2012, Michael S. Tsirkin wrote:
> >
> > +/*
> > + * Create a virtual mapping cookie for a port on a given PCI device.
> > + * Do not call this directly, it exists to make it easier for architectures
> > + * to override.
> > + */
> > +#ifdef CONFIG_NO_GENERIC_PCI_IOPORT_MAP
> > +extern void __iomem *__pci_ioport_map(struct pci_dev *dev, unsigned long port,
> > + unsigned int nr);
> > +#else
> > +static inline void __iomem *__pci_ioport_map(struct pci_dev *dev,
> > + unsigned long port, unsigned int nr)
> > +{
> > + return ioport_map(port, nr);
> > +}
> > +#endif
> >
> > Arnd
>
> It would be nicer in that it would
> make the kernel a bit smaller for generic architectures
> but this would need to go into a separate header:
> it depends on io.h and io.h depends on pci_iomap.h.
Adding extra dependencies is not good here, I agree.
Maybe a better solution is to use a macro instead of an inline
function then:
#define __pci_ioport_map(dev, port, nr) ioport_map(port, nr)
In general, macros should be avoided, but I think it's the
best tradeoff in this case.
Arnd
--
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