From: Arjan van de Ven <arjan@infradead.org>
To: "Nallasellan, Singaravelan" <singaravelan.nallasellan@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Player Thread is not woken after period elapsed
Date: Tue, 6 Sep 2011 20:06:14 -0700 [thread overview]
Message-ID: <20110906200614.57a99d3d@infradead.org> (raw)
In-Reply-To: <3CA6C6D9F70D314CA34352990B57DA1507C4275D58@bgsmsx502.gar.corp.intel.com>
> >
> > Please always test bugs like this with a recent kernel. 2.6.35 is
> > pretty much 6 versions (and 18 months) behind and at that point you
> > really have to test with something newer first before asking others
> > to help you and spend their time on your problem.
> >
> Unfortunately, I am stuck with that version as the product that I
> work on is on that version.
and that is everyone elses problem ... how?
if you can't be bothered to try at least a recent kernel, why would
anyone else be bothered to help you on their own time?????
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2011-09-07 3:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 17:38 Player Thread is not woken after period elapsed Nallasellan, Singaravelan
2011-09-05 17:52 ` Arjan van de Ven
2011-09-05 18:08 ` Nallasellan, Singaravelan
2011-09-05 18:22 ` Arjan van de Ven
2011-09-06 14:19 ` Nallasellan, Singaravelan
2011-09-07 3:06 ` Arjan van de Ven [this message]
2011-09-07 12:02 ` Nallasellan, Singaravelan
2011-09-08 2:13 ` Yong Zhang
2011-09-08 7:29 ` Yong Zhang
2011-09-08 9:45 ` Nallasellan, Singaravelan
2011-09-09 6:07 ` Yong Zhang
2011-09-09 12:42 ` Nallasellan, Singaravelan
2011-09-14 8:39 ` Yong Zhang
2011-09-14 9:18 ` Shan Hai
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=20110906200614.57a99d3d@infradead.org \
--to=arjan@infradead.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=singaravelan.nallasellan@intel.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