Hi! > I'm getting this (on ppc32, though I don't think it matters): > > CC drivers/video/chipsfb.o > drivers/video/chipsfb.c: In function `chipsfb_pci_suspend': > drivers/video/chipsfb.c:465: error: invalid operands to binary == > drivers/video/chipsfb.c:467: error: invalid operands to binary != > make[3]: *** [drivers/video/chipsfb.o] Error 1 > make[2]: *** [drivers/video] Error 2 > make[1]: *** [drivers] Error 2 > make[1]: Leaving directory > `/usr/src/linux-ctesiphon/linux-2.6.13-rc3-mm1' > make: *** [stamp-build] Error 2 > > The above-quoted patches seem to be the culprit, but my feeble > attempts at making a patch didn't work out.
Should be easy. Just add .event at right places... > But I can't help but notice that every linux-suspend HOWTO tells > you to patch in swsusp2 as a first step -- the consensus seems to be > that it you want clean and conservative code, use swsusp1; if you want > suspending to *work*, use swsusp2. How many people are actually able > to make use of swsusp1? Is anyone testing it besides Mr. Machek? SuSE ships it in production, so I believe we have at least as many users as suspend2... Pavel -- teflon -- maybe it is a trademark, but it should not be. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/