From: Julian Scheel <julian@jusst.de>
To: Eugeniu Rosca <roscaeugeniu@gmail.com>,
Felipe Balbi <balbi@kernel.org>,
Felipe Balbi <felipe.balbi@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: Re: [PATCHv2 3/3] usb: gadget: f_uac*: Support multiple sampling rates
Date: Mon, 2 Jul 2018 16:07:19 +0200 [thread overview]
Message-ID: <2333fe05-da2e-e6f6-931a-16fce2980f17@jusst.de> (raw)
In-Reply-To: <20180630181638.GA8807@x230>
Hi Eugeniu,
On 30.06.2018 20:16, Eugeniu Rosca wrote:
> Would it be possible to revive the uac2 multiple sampling rate
> patch-set [1] by rebasing it onto the most recent kernel? If you
> don't have time for this, I could help you.
I have this on my todo-list for a while now... In fact I fixed the build
errors reported by the robot last year, but didn't had the time to
verify all of it and push again.
Still, I'd be happy to get this merged, so I'll try to check the state
of this within the next days and either post to the list or get back to
you if more work needs to be done.
Best,
Julian
next prev parent reply other threads:[~2018-07-02 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 7:35 [PATCH 0/3] USB Audio Gadget: " Julian Scheel
2017-06-26 7:35 ` [PATCH 1/3] usb: gadget: f_uac1: Fix endpoint reading Julian Scheel
2017-06-26 7:35 ` [PATCH 2/3] usb: gadget: f_uac*: Reduce code duplication Julian Scheel
2017-06-26 23:39 ` kbuild test robot
2017-06-26 7:35 ` [PATCH 3/3] usb: gadget: f_uac*: Support multiple sampling rates Julian Scheel
2018-06-30 18:16 ` [PATCHv2 " Eugeniu Rosca
2018-07-02 14:07 ` Julian Scheel [this message]
2018-07-02 16:30 ` Eugeniu Rosca
2018-07-02 22:29 ` Ruslan Bilovol
2018-07-05 23:06 ` Eugeniu Rosca
2017-06-30 10:00 [PATCHv2 0/3] USB Audio Gadget: " Julian Scheel
2017-06-30 10:00 ` [PATCHv2 3/3] usb: gadget: f_uac*: " Julian Scheel
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=2333fe05-da2e-e6f6-931a-16fce2980f17@jusst.de \
--to=julian@jusst.de \
--cc=balbi@kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=roscaeugeniu@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
all inboxes | Powered by JetHome®