From: Russell King <rmk@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Patrick Mochel <mochel@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: What happened to SUSPEND_SAVE_STATE?
Date: Wed, 10 Sep 2003 23:22:57 +0100 [thread overview]
Message-ID: <20030910232257.N30046@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030910201124.GA11449@elf.ucw.cz>; from pavel@ucw.cz on Wed, Sep 10, 2003 at 10:11:26PM +0200
On Wed, Sep 10, 2003 at 10:11:26PM +0200, Pavel Machek wrote:
> pcmcia_socket_dev_suspend() still expects to receive it, but I do not
> see any place where it is generated. Should it be killed from
> device.h? And these 6 places fixed?
I've already fixed many of them, but I've introduced some others.
PPC people need to answer this:
> ./arch/ppc/ocp/ocp-driver.c: if (level == SUSPEND_SAVE_STATE && ocp_dev->driver->save_state)
Fix pending merging:
> ./arch/arm/mach-sa1100/neponset.c: if (level == SUSPEND_SAVE_STATE ||
These two will be gone shortly:
> ./drivers/pcmcia/i82092.c: return pcmcia_socket_dev_suspend(&dev->dev, state, SUSPEND_SAVE_STATE);
> ./drivers/pcmcia/sa1111_generic.c: return pcmcia_socket_dev_suspend(&dev->dev, state, SUSPEND_SAVE_STATE);
These two are already gone:
> ./drivers/serial/8250_pci.c: serial8250_suspend_port(priv->line[i], SUSPEND_SAVE_STATE);
> ./drivers/serial/core.c: case SUSPEND_SAVE_STATE:
--
Russell King (rmk@arm.linux.org.uk) http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
2.6 ARM Linux - http://www.arm.linux.org.uk/
2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
prev parent reply other threads:[~2003-09-10 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 20:11 Pavel Machek
2003-09-10 20:49 ` Pavel Machek
2003-09-10 22:25 ` Russell King
2003-09-10 22:36 ` Pavel Machek
2003-09-10 22:41 ` Russell King
2003-09-10 23:06 ` Pavel Machek
2003-09-10 22:22 ` Russell King [this message]
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=20030910232257.N30046@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®