All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: Pavel Machek <pavel@ucw.cz>,
	"Prakash K. Cheemplavam" <prakashpublic@gmx.de>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: FYI: My current suspend bigdiff
Date: Sun, 30 Nov 2003 12:24:48 -0500	[thread overview]
Message-ID: <3FCA27E0.5040809@pobox.com> (raw)
In-Reply-To: <20031130172134.GB10679@suse.de>

Jens Axboe wrote:
> Curious - can't this be put some place a bit smarter, so we don't have
> to update every single "driver" with a kernel thread out there (like in
> the scheduler)? Seems pretty fragile to rely on this. Plus, when you
> change this in the future there'll be N drivers to update again.


Agreed.  I had to do this simple and obvious (and template-able) patch 
for 8139too and another driver whose name I forget ATM...

	Jeff




  reply	other threads:[~2003-11-30 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031128171323.GG303@elf.ucw.cz>
     [not found] ` <3FC7860C.2060505@gmx.de>
     [not found]   ` <20031128173312.GH303@elf.ucw.cz>
     [not found]     ` <3FC789F5.2000208@gmx.de>
     [not found]       ` <20031128175503.GB18072@elf.ucw.cz>
     [not found]         ` <3FC7908A.9030007@gmx.de>
     [not found]           ` <20031128235623.GB18147@elf.ucw.cz>
     [not found]             ` <3FC8C0DB.9050107@gmx.de>
     [not found]               ` <20031129172537.GB459@elf.ucw.cz>
     [not found]                 ` <3FC9C560.2070902@gmx.de>
2003-11-30 17:18                   ` FYI: My current suspend bigdiff Pavel Machek
2003-11-30 17:21                     ` Jens Axboe
2003-11-30 17:24                       ` Jeff Garzik [this message]
2003-11-30 17:22                     ` Prakash K. Cheemplavam
2003-11-30 17:25                       ` Jeff Garzik
2003-11-30 17:35                         ` Pavel Machek
2003-12-01  0:09                         ` Benjamin Herrenschmidt
2003-11-24 11:07 Pavel Machek

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=3FCA27E0.5040809@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=prakashpublic@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.