Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752557AbbBOXE7 (ORCPT ); Sun, 15 Feb 2015 18:04:59 -0500 Received: from netrider.rowland.org ([192.131.102.5]:44649 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1750954AbbBOXE6 (ORCPT ); Sun, 15 Feb 2015 18:04:58 -0500 Date: Sun, 15 Feb 2015 18:04:57 -0500 (EST) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Ruslan Bilovol cc: balbi@ti.com, , , , , Subject: Re: [PATCH v2 0/2] usb/gadget: independent registration of gadgets and gadget In-Reply-To: <1424041083-23694-1-git-send-email-ruslan.bilovol@gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 32 On Mon, 16 Feb 2015, Ruslan Bilovol wrote: > This patchset adds independent registration of gadgets > and gadget drivers to udc-core. This is very useful for > built-in modules into kernel case since it's possible > situation that gadget driver is probing at a time > when no gadgets are registered in udc-core. > In this case instead of silently failing without > of any attempt to recover, with independent registration > of gadgets and gadget drivers there is no matter > in which order gadgets and gadget drivers are > probed/registered. > > This patch has side-effect on gadget drivers that had > __init/__exit attributes on some paths like bind/unbind > and (since bind/unbind may happen at any time) should > not use them now. This is covered by second patch > (please let me know if I need to break it into separate > patches for each gadget driver) The two patches should be in the opposite order. Otherwise someone might apply the first patch but not the second, and then the gadget drivers would crash when their bind/unbind routines were called at the wrong time. Alan Stern -- 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/