From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@zip.com.au>,
kernel list <linux-kernel@vger.kernel.org>
Subject: fix u32 vs. pm_message_t in driver/video
Date: Tue, 5 Apr 2005 23:45:37 +0200 [thread overview]
Message-ID: <20050405214537.GA1861@elf.ucw.cz> (raw)
Hi!
This fixes u32 vs. pm_message_t confusion in drivers/video. Should
change no code. Please apply,
Pavel
Signed-off-by: Pavel Machek <pavel@suse.cz>
--- clean-mm/drivers/video/backlight/corgi_bl.c 2005-03-19 00:31:59.000000000 +0100
+++ linux-mm/drivers/video/backlight/corgi_bl.c 2005-04-05 12:13:38.000000000 +0200
@@ -81,7 +81,7 @@
}
#ifdef CONFIG_PM
-static int corgibl_suspend(struct device *dev, u32 state, u32 level)
+static int corgibl_suspend(struct device *dev, pm_message_t state, u32 level)
{
if (level == SUSPEND_POWER_DOWN)
corgibl_blank(FB_BLANK_POWERDOWN);
--- clean-mm/drivers/video/pxafb.c 2005-04-05 10:55:24.000000000 +0200
+++ linux-mm/drivers/video/pxafb.c 2005-04-05 12:13:38.000000000 +0200
@@ -942,7 +942,7 @@
* Power management hooks. Note that we won't be called from IRQ context,
* unlike the blank functions above, so we may sleep.
*/
-static int pxafb_suspend(struct device *dev, u32 state, u32 level)
+static int pxafb_suspend(struct device *dev, pm_message_t state, u32 level)
{
struct pxafb_info *fbi = dev_get_drvdata(dev);
--- clean-mm/drivers/video/sa1100fb.c 2005-04-05 10:55:24.000000000 +0200
+++ linux-mm/drivers/video/sa1100fb.c 2005-04-05 12:13:38.000000000 +0200
@@ -1307,7 +1307,7 @@
* Power management hooks. Note that we won't be called from IRQ context,
* unlike the blank functions above, so we may sleep.
*/
-static int sa1100fb_suspend(struct device *dev, u32 state, u32 level)
+static int sa1100fb_suspend(struct device *dev, pm_message_t state, u32 level)
{
struct sa1100fb_info *fbi = dev_get_drvdata(dev);
--- clean-mm/drivers/video/savage/savagefb_driver.c 2005-04-05 10:55:24.000000000 +0200
+++ linux-mm/drivers/video/savage/savagefb_driver.c 2005-04-05 12:13:38.000000000 +0200
@@ -2103,7 +2103,7 @@
}
}
-static int savagefb_suspend (struct pci_dev* dev, u32 state)
+static int savagefb_suspend (struct pci_dev* dev, pm_message_t state)
{
struct fb_info *info =
(struct fb_info *)pci_get_drvdata(dev);
@@ -2118,7 +2118,7 @@
release_console_sem();
pci_disable_device(dev);
- pci_set_power_state(dev, state);
+ pci_set_power_state(dev, pci_choose_state(dev, state));
return 0;
}
--- clean-mm/drivers/video/w100fb.c 2005-04-05 10:55:24.000000000 +0200
+++ linux-mm/drivers/video/w100fb.c 2005-04-05 12:13:38.000000000 +0200
@@ -544,7 +544,7 @@
#ifdef CONFIG_PM
-static int w100fb_suspend(struct device *dev, u32 state, u32 level)
+static int w100fb_suspend(struct device *dev, pm_message_t state, u32 level)
{
if (level == SUSPEND_POWER_DOWN) {
struct fb_info *info = dev_get_drvdata(dev);
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
reply other threads:[~2005-04-05 21:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050405214537.GA1861@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
/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®