mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Jeff Chua" <jeff.chua.linux@gmail.com>
Cc: "Eli Collins" <ecollins@vmware.com>,
	petr@vmware.com, "H. Peter Anvin" <hpa@zytor.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: please revert commit 53f1b1433da7eac2607a4a0898a221a4485fd732 (rtc: push the BKL down into the driver ioctl method)
Date: Wed, 30 Jul 2008 09:32:16 +0100	[thread overview]
Message-ID: <20080730093216.6cbaf99c@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <b6a2187b0807291819s595685bfod3ba53b6720b4cf0@mail.gmail.com>

On Wed, 30 Jul 2008 09:19:55 +0800
"Jeff Chua" <jeff.chua.linux@gmail.com> wrote:

> On Wed, Jul 30, 2008 at 7:21 AM, Eli Collins <ecollins@vmware.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

      reply	other threads:[~2008-07-30  8:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 14:26 Jeff Chua
2008-07-25 14:48 ` Alan Cox
2008-07-25 15:55 ` H. Peter Anvin
2008-07-26  2:18   ` Jeff Chua
2008-07-26  2:52     ` H. Peter Anvin
2008-07-29 23:21     ` Eli Collins
2008-07-30  1:19       ` Jeff Chua
2008-07-30  8:32         ` Alan Cox [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080730093216.6cbaf99c@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ecollins@vmware.com \
    --cc=hpa@zytor.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petr@vmware.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®