From: Brian Bloniarz <brian.bloniarz@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC PATCH] theory about CS8247 failed reads
Date: Tue, 18 Jan 2011 10:39:48 -0800 [thread overview]
Message-ID: <4D35DE74.6030307@gmail.com> (raw)
In-Reply-To: <s5hr5cagumg.wl%tiwai@suse.de>
On 01/18/2011 06:21 AM, Takashi Iwai wrote:
> Yes, your fix looks sane (and safe).
> I'll queue it up later for 2.6.38 merge.
Sounds great, thanks!
> The retry-code can be kept for a while as it's basically harmless for
> the succeeded case. We can remove it eventually later, but I doubt we
> can be 100% sure about such a thing ;)
Sure, that makes sense to me.
Thanks,
-Brian
prev parent reply other threads:[~2011-01-18 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 7:20 [RFC PATCH] theory about CS8247 failed reads Brian Bloniarz
2011-01-18 14:21 ` Takashi Iwai
2011-01-18 18:39 ` Brian Bloniarz [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=4D35DE74.6030307@gmail.com \
--to=brian.bloniarz@gmail.com \
--cc=alsa-devel@alsa-project.org \
--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).