From: Arjan van de Ven <arjanv@redhat.com>
To: David L <idht4n@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad: scheduling while atomic!: how bad?
Date: Sun, 19 Jun 2005 01:46:52 +0200 [thread overview]
Message-ID: <20050618234651.GD23688@devserv.devel.redhat.com> (raw)
In-Reply-To: <BAY104-F295AF1E9F80CC64DDEF85784F70@phx.gbl>
On Sat, Jun 18, 2005 at 04:19:58PM -0700, David L wrote:
> >that's only part of the source though... can you point at the full one ?
>
> I'm pretty sure that's all the source... there was some documentation that
the sources for CLlogic2 and CLlogic3 are missing....
next prev parent reply other threads:[~2005-06-18 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 21:59 bad: scheduling while atomic!: how bad? David L
2005-06-18 22:10 ` Arjan van de Ven
2005-06-18 22:49 ` David L
2005-06-18 22:52 ` Arjan van de Ven
2005-06-18 23:19 ` David L
2005-06-18 23:46 ` Arjan van de Ven [this message]
2005-06-18 22:18 ` Lee Revell
2005-06-18 22:33 ` David L
2005-06-19 0:50 ` Lee Revell
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=20050618234651.GD23688@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=idht4n@hotmail.com \
--cc=linux-kernel@vger.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