[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1170500882.31373.47.camel@funkylaptop>
Date: Sat, 03 Feb 2007 12:08:01 +0100
From: Frédéric RISS <frederic.riss@...il.com>
To: Andi Kleen <ak@...e.de>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Matt Domsch <Matt_Domsch@...l.com>,
Adrian Bunk <bunk@...sta.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Eric Van Hensbergen <ericvh@...il.com>,
Trond Myklebust <trond.myklebust@....uio.no>,
Neil Brown <neilb@...e.de>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Jeff Garzik <jeff@...zik.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Francois Romieu <romieu@...zoreil.com>
Subject: Re: 2.6.20-rc7: known regressions
Le samedi 03 février 2007 à 11:57 +0100, Frédéric Riss a écrit :
> Le samedi 03 février 2007 à 11:51 +0100, Andi Kleen a écrit :
> > > +
> > > +typedef efilinkage efi_status_t efi_get_time_t (efi_time_t *tm,
> > > + efi_time_cap_t *tc);
> >
> > I assume you have double checked it actually works? (i vaguely recall some
> > issues with applying attributes to typedefs). If not you would need
> > to put them to the declarations.
>
> Of course, I tested 10 suspend/resume cycles. This is with gcc 4.1.2, I
> guess other compilers could mishandle it. Would you prefer the version
> putting asmlinkage inside the struct definition?
But then it then throws 'assignment from incompatible pointer type'
warnings in efi.c. This would need fixing in arch/ia64 and arch/i386. Or
should I put it in the typdefs _and_ in the struct to be safe ?
Fred
-
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