public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Frank <mhf@linuxmail.org>
Cc: Micha Feigin <michf@post.tau.ac.il>,
	Software suspend <swsusp-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] Re: Dropping CONFIG_PM_DISK?
Date: Tue, 02 Mar 2004 09:10:22 +1100	[thread overview]
Message-ID: <1078179022.21573.136.camel@gaston> (raw)
In-Reply-To: <opr36ojxik4evsfm@smtp.pacific.net.th>


> Appreciated, suspending a driver like sending XOFF to a tty is ideal,
> but not neccessary for _most_ drivers (software suspend) purpose.
> 
> Wrt IDE, in practice all processes get frozen well before
> suspending drivers. Tested and no issues were ever reported with 2.4.

It is still fragile. I have seen IDE requests slipping in anyway.

But IDE isn't a problem, I wrote a working PM implementation for
IDE in 2.6. 

> > Moving to the new model is easy. I don't see why we should have had
> > such a "compatibility" path on a major kernel version, that makes
> > no sense, just help fixing the drivers that need more fixing instead.
> 
> What for write new drivers for (fast obsoleting) hardware?.

Ok, you are at troll, no need to argue more.




  parent reply	other threads:[~2004-03-01 22:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ulUA-33w-3@gated-at.bofh.it>
2004-02-29 16:17 ` Dropping CONFIG_PM_DISK? Karol Kozimor
2004-02-29 16:23   ` Pavel Machek
2004-02-29 17:32     ` Måns Rullgård
2004-02-29 18:10       ` Michael Frank
2004-02-29 21:33         ` [Swsusp-devel] " Micha Feigin
2004-03-01  2:51           ` Michael Frank
2004-03-01 11:09             ` Benjamin Herrenschmidt
2004-03-01 11:35               ` Karol Kozimor
2004-03-01 11:28                 ` Benjamin Herrenschmidt
2004-03-01 11:51                   ` Karol Kozimor
2004-03-01 12:56                     ` Martin Wickman
2004-03-01 13:22                       ` Michael Frank
2004-03-01 12:34                   ` Micha Feigin
2004-03-01 11:31                 ` Benjamin Herrenschmidt
2004-03-01 11:57                   ` Karol Kozimor
2004-03-01 22:08                     ` Benjamin Herrenschmidt
2004-03-01 11:43               ` Michael Frank
2004-03-01 11:39                 ` Benjamin Herrenschmidt
2004-03-01 12:48                   ` Michael Frank
2004-03-01 13:47                     ` Arjan van de Ven
2004-03-01 14:33                       ` Michael Frank
2004-03-01 14:38                         ` Arjan van de Ven
2004-03-01 22:10                     ` Benjamin Herrenschmidt [this message]
2004-02-29 18:10       ` Pavel Machek
2004-02-29 18:29         ` Måns Rullgård
2004-03-01  9:40           ` Pavel Machek
2004-03-01 10:08             ` Måns Rullgård
2004-03-01 10:39               ` Pavel Machek
2004-03-01  9:58                 ` Nigel Cunningham
2004-03-01 12:46                   ` Pavel Machek
2004-03-01 18:16                     ` Nigel Cunningham
2004-03-01 20:22                       ` Pavel Machek
2004-03-01 10:45               ` Michael Frank
2004-03-03  1:53 [Swsusp-devel] " John Mock

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=1078179022.21573.136.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.org \
    --cc=michf@post.tau.ac.il \
    --cc=swsusp-devel@lists.sourceforge.net \
    /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