From: Felipe Ferreri Tonello <eu@felipetonello.com>
To: Michal Nazarewicz <mina86@mina86.com>, Felipe Balbi <balbi@ti.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Robert Baldyga <r.baldyga@samsung.com>,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, "Du,
Changbin" <changbin.du@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCHv3 00/11] Fixes and improvements to f_fs and f_midi
Date: Wed, 3 Feb 2016 10:06:12 +0000 [thread overview]
Message-ID: <56B1D114.7090704@felipetonello.com> (raw)
In-Reply-To: <1453820003-1441-1-git-send-email-mina86@mina86.com>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hi Michal,
On 26/01/16 14:53, Michal Nazarewicz wrote:
> Resending my previous two sets for f_fs and f_midi. This time rebased
> on top of Felipe’s next branch.
>
> Dan Carpenter (1):
> usb: gadget: f_midi: missing unlock on error path
>
> Du, Changbin (1):
> usb: f_fs: avoid race condition with ffs_epfile_io_complete
>
> Felipe F. Tonello (1):
> usb: gadget: f_midi: remove useless midi reference from port struct
>
> Michal Nazarewicz (8):
> usb: f_fs: fix memory leak when ep changes during transfer
> usb: f_fs: fix ffs_epfile_io returning success on req alloc failure
> usb: f_fs: replace unnecessary goto with a return
> usb: f_fs: refactor ffs_epfile_io
> usb: gadget: f_midi: move some of f_midi_transmit to separate func
> usb: gadget: f_midi: fix in_last_port looping logic
> usb: gadget: f_midi: use flexible array member for gmidi_in_port
> elements
> usb: gadget: f_midi: stash substream in gmidi_in_port structure
Sorry for the delay, but I will look into your patches related to f_midi
this week.
>
> drivers/usb/gadget/function/f_fs.c | 155 +++++++++++++--------------
> drivers/usb/gadget/function/f_midi.c | 200 ++++++++++++++++-------------------
> 2 files changed, 164 insertions(+), 191 deletions(-)
>
--
Felipe
[-- Attachment #2: 0x92698E6A.asc --]
[-- Type: application/pgp-keys, Size: 7195 bytes --]
next prev parent reply other threads:[~2016-02-03 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 14:53 Michal Nazarewicz
2016-02-03 10:06 ` Felipe Ferreri Tonello [this message]
2016-02-18 21:21 ` Felipe Balbi
2016-02-18 21:56 ` Michal Nazarewicz
2016-02-19 7:12 ` Felipe Balbi
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=56B1D114.7090704@felipetonello.com \
--to=eu@felipetonello.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=changbin.du@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mina86@mina86.com \
--cc=r.baldyga@samsung.com \
/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
Powered by JetHome