Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753831AbaAWVKN (ORCPT ); Thu, 23 Jan 2014 16:10:13 -0500 Received: from mail-pa0-f54.google.com ([209.85.220.54]:57315 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751492AbaAWVKK (ORCPT ); Thu, 23 Jan 2014 16:10:10 -0500 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 23 Jan 2014 23:10:09 +0200 Message-ID: Subject: Re: [PATCH] staging: usbip: convert usbip-host driver to usb_device_driver From: Valentina Manea To: Alan Stern Cc: Greg KH , Anthony Foiani , devel@driverdev.osuosl.org, navinp@cdac.in, linux-usb@vger.kernel.org, ly80toro@cip.cs.fau.de, josh@joshtriplett.org, linux-kernel@vger.kernel.org, "Linux Kernel Community @ ROSEdu" , =?UTF-8?B?VMO8bGluIMSwemVy?= , yacine.belkadi.1@gmail.com, ke42caxa@cip.cs.fau.de Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > If you don't bind the interfaces, they will naturally bind to their > normal drivers on the host. You probably don't want that to happen. > (Although, at the moment, I don't see how you can prevent it.) > That's true but, the way I see USB/IP general use case, the drivers from the host the device is physically attached to won't even be actually used, since the host doesn't use the device. However, I can't think of a way to enforce this. > Also, in your patch, stub_probe() calls usb_choose_configuration(). > Shouldn't that be done by the client, since the client now has access > to the entire device? I think the normal user just wants things *to work*. Surely, for advanced user an option for choosing the configuration could be added but I, personally, don't see it as a necessity at this point. Thanks, Valentina -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/