Fix u32 vs. pm_message_t confusion in serials

[Pavel Machek]

Hi!

This fixes u32 vs. pm_message_t confusion in serials. Please apply,

								Pavel
Signed-off-by: Pavel Machek <pavel@xxxxxxx>

--- clean-mm/drivers/serial/8250.c	2005-02-15 00:46:41.000000000 +0100
+++ linux-mm/drivers/serial/8250.c	2005-02-15 01:04:10.000000000 +0100
@@ -2316,7 +2316,7 @@
 	return 0;
 }
 
-static int serial8250_suspend(struct device *dev, u32 state, u32 level)
+static int serial8250_suspend(struct device *dev, pm_message_t state, u32 level)
 {
 	int i;
 
--- clean-mm/drivers/serial/8250_pci.c	2004-12-25 13:35:01.000000000 +0100
+++ linux-mm/drivers/serial/8250_pci.c	2005-02-15 01:04:10.000000000 +0100
@@ -1759,7 +1759,7 @@
 	}
 }
 
-static int pciserial_suspend_one(struct pci_dev *dev, u32 state)
+static int pciserial_suspend_one(struct pci_dev *dev, pm_message_t state)
 {
 	struct serial_private *priv = pci_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!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/