From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Fixes for ide-disk.c
Date: Fri, 11 Apr 2003 11:36:56 +1200 [thread overview]
Message-ID: <1050017816.2629.8.camel@laptop-linux.cunninghams> (raw)
In-Reply-To: <1050011724.12930.138.camel@dhcp22.swansea.linux.org.uk>
Hi.
As far as ide code goes, I'm trying to:
1) Get rid of messages that don't need to appear during suspend (so the
'nice display' looks nice (hence printk changes)
2) Make sure the data actually does make it to disk before we poweroff
(hence write back cache interest)
3) Make sure ide_suspend/unsuspend do the right thing (however that's
defined).
I hadn't looked at the code yet to see why it's called twice - too busy
with other things. I did wonder if
device_suspend(4, SUSPEND_NOTIFY);
device_suspend(4, SUSPEND_SAVE_STATE);
device_suspend(4, SUSPEND_DISABLE);
might do it, but it's an untested theory.
Regards,
Nigel
On Fri, 2003-04-11 at 09:55, Alan Cox wrote:
> On Thu, 2003-04-10 at 19:38, Pavel Machek wrote:
> > Hi!
> >
> > > > Okay. We need a different solution then, but the problem remains - the
> > > > driver can get multiple, nexted calls to block and unblock. Can it
> > > > become a counting lock?
> > >
> > > Blocked is a binary power management described state, its not a lock.
> > > What are you actually trying to do ?
> >
> > He's trying to fix swsusp. Just now it likes
> > to BUG() for some people.
>
> I meant at a slightly lower and more detailed level
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
Be diligent to present yourself approved to God as a workman who does
not need to be ashamed, handling accurately the word of truth.
-- 2 Timothy 2:14, NASB.
next prev parent reply other threads:[~2003-04-10 23:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 7:31 PATCH: Fixes for ide-disk.c Nigel Cunningham
2003-04-05 9:27 ` John Bradford
2003-04-05 10:57 ` Andre Hedrick
2003-04-05 13:09 ` John Bradford
2003-04-05 16:46 ` Alan Cox
2003-04-05 19:25 ` Nigel Cunningham
2003-04-05 20:58 ` Andre Hedrick
2003-04-06 15:03 ` Alan Cox
2003-04-06 20:59 ` Nigel Cunningham
2003-04-06 21:02 ` Alan Cox
2003-04-06 21:12 ` Nigel Cunningham
2003-04-06 21:00 ` Alan Cox
2003-04-06 21:58 ` Nigel Cunningham
2003-04-10 18:38 ` Pavel Machek
2003-04-10 21:55 ` Alan Cox
2003-04-10 23:36 ` Nigel Cunningham [this message]
2003-04-13 11:17 ` Pavel Machek
2003-04-10 18:37 ` Pavel Machek
2003-04-11 3:30 ` Andre Hedrick
2003-04-05 16:46 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-04-05 10:32 Chuck Ebbert
2003-04-05 11:30 ` Andre Hedrick
2003-04-05 18:34 Mudama, Eric
2003-04-05 19:52 ` Andre Hedrick
2003-04-05 20:17 Mudama, Eric
2003-04-05 20:54 ` Andre Hedrick
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=1050017816.2629.8.camel@laptop-linux.cunninghams \
--to=ncunningham@clear.net.nz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.