From: Lauri Kasanen <cand@gmx.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-mips@vger.kernel.org, tsbogend@alpha.franken.de, perex@perex.cz
Subject: Re: [PATCH 5/6 v2] sound: Add n64 driver
Date: Wed, 13 Jan 2021 14:49:58 +0200 [thread overview]
Message-ID: <20210113144958.8445eec4e15c0376520646cd@gmx.com> (raw)
In-Reply-To: <s5him81nhac.wl-tiwai@suse.de>
On Wed, 13 Jan 2021 13:38:19 +0100
Takashi Iwai <tiwai@suse.de> wrote:
> > The other point is that memcpy doesn't have a downside now - it doesn't
> > crackle when properly double-buffered. It's simpler this way vs
> > workqueues/etc.
>
> I'm fine with the other workaround as long as it works effectively.
> It needs more description in the code, though :)
v4 has a comment about that in push(). Can you review v4 and point out
where it needs more comments?
- Lauri
prev parent reply other threads:[~2021-01-13 12:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 8:35 [PATCH 5/6 v2] sound: Add n64 driver Lauri Kasanen
2021-01-08 9:06 ` Takashi Iwai
2021-01-08 10:13 ` Lauri Kasanen
2021-01-09 7:23 ` Lauri Kasanen
2021-01-09 8:16 ` Takashi Iwai
2021-01-09 17:46 ` Lauri Kasanen
2021-01-09 18:17 ` Takashi Iwai
2021-01-09 20:54 ` Takashi Iwai
2021-01-10 7:15 ` Lauri Kasanen
2021-01-10 10:24 ` Takashi Iwai
2021-01-10 17:03 ` Lauri Kasanen
2021-01-10 17:22 ` Takashi Iwai
2021-01-10 17:41 ` Lauri Kasanen
2021-01-11 8:05 ` Takashi Iwai
2021-01-11 9:43 ` Lauri Kasanen
2021-01-11 10:11 ` Takashi Iwai
2021-01-11 12:02 ` Lauri Kasanen
2021-01-11 15:25 ` Takashi Iwai
2021-01-11 15:51 ` Lauri Kasanen
2021-01-13 11:57 ` Lauri Kasanen
2021-01-13 12:04 ` Takashi Iwai
2021-01-13 12:14 ` Lauri Kasanen
2021-01-13 12:38 ` Takashi Iwai
2021-01-13 12:49 ` Lauri Kasanen [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=20210113144958.8445eec4e15c0376520646cd@gmx.com \
--to=cand@gmx.com \
--cc=linux-mips@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=tsbogend@alpha.franken.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