From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: ext Tejun Heo <tj@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: workqueues tree build failure
Date: Thu, 26 Nov 2009 13:44:31 +0200 [thread overview]
Message-ID: <200911261344.32051.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <20091126101859.GA27562@rakim.wolfsonmicro.main>
On Thursday 26 November 2009 12:18:59 ext Mark Brown wrote:
> On Thu, Nov 26, 2009 at 11:31:15AM +0200, Peter Ujfalusi wrote:
> > For a quick fix, I can convert the tlv320dac33 driver to use this, and
> > revisit later, if it does not fulfill the timing requirements for the HW.
>
> If there are problems then creating a dedicated thread you can wake
> would probably do the job.
For now I'm going to change the create_rt_workqueue to
create_singlethread_workqueue, that is available at the wq.git of kernel.org.
If it is not sufficient, than I might use dedicated thread, which I woke up, but
I would like to keep that as a backup plan, since it needs more work ;)
I'll send the patch in a few minutes.
--
Péter
next prev parent reply other threads:[~2009-11-26 11:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 8:00 linux-next: workqueues tree build failure Stephen Rothwell
2009-11-26 8:04 ` Tejun Heo
2009-11-26 8:16 ` Peter Ujfalusi
2009-11-26 9:12 ` Tejun Heo
2009-11-26 9:24 ` Takashi Iwai
2009-11-26 9:31 ` Peter Ujfalusi
2009-11-26 10:18 ` Mark Brown
2009-11-26 11:44 ` Peter Ujfalusi [this message]
2009-11-26 12:49 ` Andy Walls
2009-11-26 13:23 ` Peter Ujfalusi
2009-11-26 12:40 ` Andy Walls
2009-11-26 12:56 ` Mark Brown
2009-11-27 2:02 ` Tejun Heo
2009-11-27 8:37 ` Takashi Iwai
2009-11-27 8:42 ` Tejun Heo
2009-11-27 10:09 ` Peter Ujfalusi
2009-11-27 11:38 ` Mark Brown
2009-11-27 13:50 ` Andy Walls
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=200911261344.32051.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
--cc=tj@kernel.org \
/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).