From: Daniel Mack <daniel@zonque.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: orm.finnendahl@selma.hfmdk-frankfurt.de,
alsa-devel@alsa-project.org, clemens@ladisch.de,
jan.baumgart@selma.hfmdk-frankfurt.de
Subject: Re: [PATCH 2/2] sound: usb: allow clock source validity interrupts
Date: Sat, 9 Apr 2016 16:37:28 +0200 [thread overview]
Message-ID: <570913A8.6090203@zonque.org> (raw)
In-Reply-To: <s5hegafcdoz.wl-tiwai@suse.de>
On 04/09/2016 11:51 AM, Takashi Iwai wrote:
> On Sat, 09 Apr 2016 11:16:59 +0200, Daniel Mack wrote:
>> On 04/09/2016 10:52 AM, Takashi Iwai wrote:
>>> Just for checking count=0 and count=1, we need no loop to count
>>> beforehand.
>>> if (info->control != control &&
>>> (list != mixer->id_elems[unit] ||
>>> list->list_next_id_elem))
>>> continue;
>>>
>>> But, this doesn't look better and is more harder to understand, so I'm
>>> not willing to sell it :)
>>
>> I had something like that before but opted for the more readable
>> version. But you're right. I'll add a comment and do it your way.
>
> Oh no, sorry, I wasn't clear: I meant that my version is worse in the
> end, and I prefer your first version, just for simplicity.
Ah ok :) Well, ultimately up to you; you have both versions, and the two
patches should apply independently anyway.
Or I can resend both if you prefer that.
Thanks,
Daniel
next prev parent reply other threads:[~2016-04-09 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 17:52 [PATCH 1/2] sound: usb: add UAC2 clock sources as mixer controls Daniel Mack
2016-04-08 17:52 ` [PATCH 2/2] sound: usb: allow clock source validity interrupts Daniel Mack
2016-04-09 8:52 ` Takashi Iwai
2016-04-09 9:16 ` Daniel Mack
2016-04-09 9:51 ` Takashi Iwai
2016-04-09 14:37 ` Daniel Mack [this message]
2016-04-09 15:25 ` Takashi Iwai
2016-04-09 8:43 ` [PATCH 1/2] sound: usb: add UAC2 clock sources as mixer controls Takashi Iwai
2016-04-09 9:09 ` Daniel Mack
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=570913A8.6090203@zonque.org \
--to=daniel@zonque.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=jan.baumgart@selma.hfmdk-frankfurt.de \
--cc=orm.finnendahl@selma.hfmdk-frankfurt.de \
--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 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).