From: Clemens Ladisch <clemens@ladisch.de>
To: Ruslan Bilovol <ruslan.bilovol@gmail.com>
Cc: Felipe Balbi <balbi@kernel.org>, Daniel Mack <zonque@gmail.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/5] USB Audio Gadget refactoring
Date: Fri, 15 Jul 2016 09:43:05 +0200 [thread overview]
Message-ID: <c737fdff-9312-add2-00bb-a8fcbcbde365@ladisch.de> (raw)
In-Reply-To: <CAB=otbRK6r2eNagQySizvozjttEdHTBD_9kdEu3xTmt8=nCZ9w@mail.gmail.com>
>> On Tue, May 24, 2016 at 2:50 AM, Ruslan Bilovol
>> <ruslan.bilovol@gmail.com> wrote:
>>> it may break current usecase for some people
And what are the benefits that justify breaking the kernel API?
Regards,
Clemens
next prev parent reply other threads:[~2016-07-15 7:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 23:50 [RFC PATCH 0/5] USB Audio Gadget refactoring Ruslan Bilovol
2016-05-23 23:50 ` [RFC PATCH 1/5] usb: gadget: f_uac2: remove platform driver/device creation Ruslan Bilovol
2016-05-23 23:50 ` [RFC PATCH 2/5] usb: gadget: f_uac2: split out audio core Ruslan Bilovol
2016-05-23 23:50 ` [RFC PATCH 3/5] usb: gadget: f_uac1: drop volume/mute functionality Ruslan Bilovol
2016-05-23 23:50 ` [RFC PATCH 4/5] usb: gadget: f_uac1: switch to u_audio core utilities Ruslan Bilovol
2016-05-23 23:50 ` [RFC PATCH 5/5] usb: gadget: f_uac1: add capture support Ruslan Bilovol
2016-06-08 8:03 ` [RFC PATCH 0/5] USB Audio Gadget refactoring Ruslan Bilovol
2016-07-14 21:38 ` Ruslan Bilovol
2016-07-15 7:43 ` Clemens Ladisch [this message]
2016-07-26 1:31 ` Ruslan Bilovol
2016-07-26 8:06 ` Clemens Ladisch
2016-07-26 21:22 ` Ruslan Bilovol
2016-07-26 8:53 ` Jassi Brar
2016-07-26 12:02 ` Krzysztof Opasiak
2016-07-26 21:55 ` Ruslan Bilovol
2016-07-26 21:38 ` Ruslan Bilovol
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=c737fdff-9312-add2-00bb-a8fcbcbde365@ladisch.de \
--to=clemens@ladisch.de \
--cc=balbi@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ruslan.bilovol@gmail.com \
--cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).