From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
saobannion@gmail.com
Subject: Re: Could I put a patch to 4.7 final?
Date: Fri, 22 Jul 2016 05:48:43 +0900 [thread overview]
Message-ID: <5791352B.70307@sakamocchi.jp> (raw)
In-Reply-To: <s5hzipbefp9.wl-tiwai@suse.de>
Hi,
On Jul 21 2016 14:13, Takashi Iwai wrote:
> On Thu, 21 Jul 2016 05:12:10 +0200,
> Takashi Sakamoto wrote:
>>
>> Iwai-san,
>>
>> Yesterday, I found an user of additional OXFW device, and we're under
>> testing a patch to support it.
>> https://sourceforge.net/p/ffado/mailman/message/35229260/
>>
>> I need one day more to post corresponding patch. The prototype is:
>> https://github.com/takaswie/snd-firewire-improve/commit/690a2419fc95766826c8d2c0964f6f099f9d65bd
>>
>> This week is final week for 4.7, but do I have a rest to add the patch
>> to it in time of your work for mainline?
>
> If the patch is a regression fix or a stable fix, I can queue it for
> 4.7-final. Others will go to 4.8-rc1.
We have similar issue before.
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-January/103167.html
I think this is a case of the 'simple addition of device IDs'.
> I'm going to send a pull request tomorrow, so please submit in time.
OK.
Probably, the model has unique quirk to lose quality of PCM substream of
current ALSA OXFW driver and I predict the patch is not in time of your
work.
Anyway, today, I wait for the tester's report.
Thanks
Takashi Sakamoto
prev parent reply other threads:[~2016-07-21 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57903D8A.5010106@sakamocchi.jp>
2016-07-21 5:13 ` Could I put a patch to 4.7 final? Takashi Iwai
2016-07-21 20:48 ` Takashi Sakamoto [this message]
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=5791352B.70307@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=saobannion@gmail.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.