[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080730093216.6cbaf99c@lxorguk.ukuu.org.uk>
Date: Wed, 30 Jul 2008 09:32:16 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: "Jeff Chua" <jeff.chua.linux@...il.com>
Cc: "Eli Collins" <ecollins@...are.com>, petr@...are.com,
"H. Peter Anvin" <hpa@...or.com>,
lkml <linux-kernel@...r.kernel.org>,
"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: please revert commit 53f1b1433da7eac2607a4a0898a221a4485fd732
(rtc: push the BKL down into the driver ioctl method)
On Wed, 30 Jul 2008 09:19:55 +0800
"Jeff Chua" <jeff.chua.linux@...il.com> wrote:
> On Wed, Jul 30, 2008 at 7:21 AM, Eli Collins <ecollins@...are.com> wrote:
>
> > The module fixes for 2.6.26+ kernels are in upcoming releases and should
> > get backported to older ones.
>
> Thanks, just let me know when it'll be available and I'll be more than
> happy to test it out for you.
>
> At the mean time, I've worked around the problem by adding back .ioctl
> that vmware is can work in 2.6.27-rc1.
Thanks for confirming this is the case. I'm intrigued to think that
vmware considers itself somehow an independant work when it goes poking
around the innards of private kernel structures in this way. I think this
breakage speaks volumes
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