public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Junfeng Yang <yjf@stanford.edu>,
	linux-kernel@vger.kernel.org, mc@cs.stanford.edu
Subject: Re: [CHECKER] 28 potential interrupt errors
Date: Sun, 18 Mar 2001 11:03:38 +1100	[thread overview]
Message-ID: <3AB3FB5A.BAA50BEA@uow.edu.au> (raw)
In-Reply-To: <Pine.GSO.4.31.0103162216360.10409-100000@elaine24.Stanford.EDU> <Pine.LNX.4.30.0103172238030.17004-100000@imladris.demon.co.uk>

David Woodhouse wrote:
> 
> [ n_r3964.c stuff ]
> ...
> akpm, were you looking at this?

I'm planning on poking through everything which has been
identified as a posible problem.  But I won't start for
several weeks - give the maintainers (if any) time to
address these things.

So.. please go ahead :)

There's another thing which needs doing to n_r3964.c, BTW - the
abuse of task queues in r3964_close().  This is, I think, the
only client of task queues which needs to poke so deeply into
the implementation internals and Linus has mentioned something about
needing to redesign the task queues in 2.5.  So n_r3964 needs
somehow to be redesigned so that it can use standard APIs.

-

  reply	other threads:[~2001-03-18  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-17  6:18 [CHECKER] 28 potential interrupt errors Junfeng Yang
2001-03-17 12:03 ` Andrew Morton
2001-03-17 21:29   ` Junfeng Yang
2001-03-17 22:42 ` David Woodhouse
2001-03-18  0:03   ` Andrew Morton [this message]
2001-03-18 13:07     ` David Woodhouse
2001-03-18 18:03     ` Kai Germaschewski
2001-03-18 11:52 ` Jeff Garzik
2001-03-19  1:53   ` Dawson Engler

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=3AB3FB5A.BAA50BEA@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mc@cs.stanford.edu \
    --cc=yjf@stanford.edu \
    /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