public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kay Sievers <kay@vrfy.org>
Subject: Re: [RFC PATCH] USB: remove CONFIG_USB_DEVICEFS
Date: Fri, 25 May 2012 06:52:49 +0900	[thread overview]
Message-ID: <20120524215249.GA17936@kroah.com> (raw)
In-Reply-To: <CAAJw_Zug=xFjzaguqfq+-HYBjmwDPJ+5Ntj=otMY4MJk2UWxDQ@mail.gmail.com>

On Thu, May 24, 2012 at 11:55:16PM +0800, Jeff Chua wrote:
> On Thu, Apr 26, 2012 at 11:12 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Thu, Apr 26, 2012 at 11:06:45AM -0400, Alan Stern wrote:
> >> On Wed, 25 Apr 2012, Greg Kroah-Hartman wrote:
> >>
> >> > This option has been deprecated for many years now, and no userspace
> >> > tools use it anymore, so it should be safe to finally remove it.
> >> >
> >> > Reported-by: Kay Sievers <kay@vrfy.org>
> >> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> >
> >> > Anyone object to me queuing this up for the 3.5 kernel release?
> >>
> >> I'm not sure about this.  There are a few systems still floating around
> >> that don't use udev; on those systems /proc/bus/usb is the only way for
> >> user programs to control USB devices.  Admittedly, I have no idea
> >> whether any such systems will be using 3.5 or later kernels...
> >
> > They don't have to use udev, they can use devtmpfs (which is what the
> > majority of embedded systems use today), or they can just use static
> > device nodes to get access to these devices, the char node is still
> > present, we aren't getting rid of them at all.
> 
> Looks like vmware is breaking. Can't find any usb devices. I'm not using udev.

vmware doesn't use usbfs, otherwise how would it be working on all of
the systems out there that haven't mounted usbfs for years?

What exactly broke?  What version of vmware are you using, and is the
problem in the guest or host?

We delayed other usbfs changes for years due to vmware "issues", it
wouldn't be the first time we've had to handle this :(

thanks,

greg k-h

  parent reply	other threads:[~2012-05-24 21:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26  0:15 [RFC PATCH] USB: remove CONFIG_USB_DEVICEFS Greg Kroah-Hartman
2012-04-26 15:06 ` Alan Stern
2012-04-26 15:12   ` Greg Kroah-Hartman
2012-05-24 15:55     ` Jeff Chua
2012-05-24 16:02       ` Alan Cox
2012-05-24 21:52       ` Greg Kroah-Hartman [this message]
2012-05-25  5:48         ` Jeff Chua
2012-05-25  6:01           ` Greg Kroah-Hartman
2012-05-25  7:06             ` Jeff Chua
2012-05-25  7:16               ` Greg Kroah-Hartman
2012-05-25  9:01                 ` Kay Sievers
2012-05-25 11:34                   ` Kay Sievers
2012-05-25 13:31                   ` Jeff Chua
2012-05-28 12:37 ` Ezequiel Garcia
2012-05-28 13:54   ` Greg Kroah-Hartman
2012-05-28 14:20     ` Ezequiel Garcia

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=20120524215249.GA17936@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jeff.chua.linux@gmail.com \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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