public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Stelian Pop <stelian.pop@fr.alcove.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 2.5.bk] allow sbp2 driver to compile again
Date: Wed, 30 Oct 2002 10:50:05 -0500	[thread overview]
Message-ID: <20021030155005.GI1521@phunnypharm.org> (raw)
In-Reply-To: <20021030144004.GI17103@tahoe.alcove-fr>

On Wed, Oct 30, 2002 at 03:40:04PM +0100, Stelian Pop wrote:
> On Wed, Oct 30, 2002 at 09:37:20AM -0500, Ben Collins wrote:
> 
> > > While we are at it, there are a lot of 'bad: scheduling while atomic!'
> > > and 'sleeping function called from illegal context' when loading
> > > the ohci1394/sbp2 drivers (detailed stack available when compiling
> > > with CONFIG_DEBUG_KERNEL)...
> > 
> > Yeah, I've noticed aswell. Problem is I don't have a machine that runs
> > 2.5.x stable enough to do some testing.
> 
> Well, it should just be stable enough to survive a modprobe ohci1394...

I don't have any i386's to test with. I'm doing all my 1394 development
on ultrasparc, and a little on ia64, parisc, and powerpc...you know,
real machines :)

I'll be able to look at this over the weekend.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

  reply	other threads:[~2002-10-30 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 14:13 [PATCH 2.5.bk] allow sbp2 driver to compile again Stelian Pop
2002-10-30 14:26 ` Ben Collins
2002-10-30 14:32   ` Stelian Pop
2002-10-30 14:37     ` Ben Collins
2002-10-30 14:40       ` Stelian Pop
2002-10-30 15:50         ` Ben Collins [this message]
2002-10-30 15:04       ` Stelian Pop

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=20021030155005.GI1521@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stelian.pop@fr.alcove.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