Messages in this thread | | | Date | Wed, 13 Jun 2007 01:38:42 +0200 | From | Adrian Bunk <> | Subject | Re: fix placement of inline keyword. |
| |
On Tue, Jun 12, 2007 at 07:30:35PM -0400, Dave Jones wrote:
> gcc gets whiney about the placement of 'inline' at some warning levels. >...
Since most of them are in C files, can you remove these when you are at it?
> --- linux-2.6.20.noarch/arch/ia64/sn/pci/pcibr/pcibr_ate.c~ 2007-04-04 19:34:50.000000000 -0400 > +++ linux-2.6.20.noarch/arch/ia64/sn/pci/pcibr/pcibr_ate.c 2007-04-04 19:34:56.000000000 -0400 > @@ -138,7 +138,7 @@ static inline u64 __iomem *pcibr_ate_add > /* > * Update the ate. > */ > -void inline > +inline void > ate_write(struct pcibus_info *pcibus_info, int ate_index, int count, > volatile u64 ate) > { >...
And some are even non-static inline functions...
cu Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |