Re: [JANITOR PROPOSAL] Switch ioctl functions to ->unlocked_ioctl II

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Andi Kleen <andi@...>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@...>, <linux-kernel@...>, <kernel-janitors@...>, <gorcunov@...>
Date: Tuesday, January 8, 2008 - 7:06 pm

> I would suggest to only work on files that compile. e.g. do a

Actually since this will probably take very long on a slower machine you can refer to 

http://halobates.de/allyes/

for some allyes buildlogs of recent kernels for i386 and x86-64. A trick to quickly check
if something compiles is also to do

make allyesconfig
make path/to/file.o 

That won't catch linker errors, but if you don't have warnings there are normally no
linker errors either.

-Andi
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [JANITOR PROPOSAL] Switch ioctl functions to -&gt;unlock..., Alasdair G Kergon, (Thu Jan 10, 7:39 am)
Re: [JANITOR PROPOSAL] Switch ioctl functions to -&gt;unlock..., Christoph Hellwig, (Thu Jan 10, 4:34 am)
Re: [JANITOR PROPOSAL] Switch ioctl functions to ->unlock..., Andi Kleen, (Tue Jan 8, 7:06 pm)