Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756752AbbLASbG (ORCPT ); Tue, 1 Dec 2015 13:31:06 -0500 Received: from mail-wm0-f41.google.com ([74.125.82.41]:38393 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755177AbbLASbE (ORCPT ); Tue, 1 Dec 2015 13:31:04 -0500 From: "Felipe F. Tonello" To: linux-usb@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Felipe Balbi , Clemens Ladisch , Greg Kroah-Hartman , Robert Baldyga Subject: [PATCH v6 0/3] USB MIDI Gadget improvements and bug fixes Date: Tue, 1 Dec 2015 18:30:59 +0000 Message-Id: <1448994662-21294-1-git-send-email-eu@felipetonello.com> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1290 Lines: 37 Fixed all comments suggested by the linux-usb list. changes in v6: - Removed patches already applied in Balbi's tree - Cleanups on pre-allocation usb requrests patch - Fixed indentention on patch 1 - Added patch which fails set_alt if a failure happened while allocating usb requests changes in v5: - Use ep->enabled insetad of creating driver specific flag - Save MIDIStreaming interface id in driver data - define free_ep_req as static inline in header changes in v4: - pre-alocation of in requests. - more code clean up - fix memory leak on out requests - configure endpoints only when setting up MIDIStreaming interface Felipe F. Tonello (3): usb: gadget: f_midi: set altsettings only for MIDIStreaming interface usb: gadget: f_midi: fail if set_alt fails to allocate requests usb: gadget: f_midi: pre-allocate IN requests drivers/usb/gadget/function/f_midi.c | 175 +++++++++++++++++++++++++++-------- drivers/usb/gadget/legacy/gmidi.c | 2 +- 2 files changed, 135 insertions(+), 42 deletions(-) -- 2.5.0 -- 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/