[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080827232803.2ba8dd96@lxorguk.ukuu.org.uk>
Date: Wed, 27 Aug 2008 23:28:03 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Peter Osterlund <petero2@...ia.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Alan Cox <alan@...hat.com>,
Jens Axboe <jens.axboe@...cle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Adrian Bunk <bunk@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Natalie Protasevich <protasnb@...il.com>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: 2.6.27-rc4-git1: Reported regressions from 2.6.26
> Btw, why is unlocked_ioctl returning "long"? Does anybody depend on that
> too? That's another difference between the "unlocked" and the traditional
> version..
I don't know - a lot of syscall returns got defined as long and I guess
someone thought propogating the right type was a good diea ?
>
> As to the "x86 cases", I think you should try to hit them all. Doing a
> "git grep unlocked_ioctl" gets 185 entries, and it looks like only
> something like 8 of them are non-x86 (3 in the arch/ directory, five in
> s390 drivers).
>
> Of course, some of them may be drivers that aren't available on x86 for
> other reasons (ie the ARM embedded stuff), but regardless..
>
> Anyway, the pure size of that patch makes me suspect that we might as well
> leave it until the next merge window, but if you do it and it's obviously
> totally mechanical, I'd be likely to just let it slip in early.
I'll take a crack at it tomorrow - but if its 185 entries then it
probably wants to go into -next instead.
Alan
--
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