Software suspend - again

Posted Feb 9, 2006 17:08 UTC (Thu) by dambacher (subscriber, #1710)
Parent article: Software suspend - again

I am really fed up with this discussions. Why can't the kernel developers think of the kernel users fortune and just let _them_ decide?

It would be so simple to just do two kconfig options for either suspend code and a 3rd for kexe/kdump/(kresume?) The better one wins.
Or all win for special purposes.
We have choice in many other places of the kernel (see schedulers), why not with the suspend code?

Sometimes the diskussion is on a niveau where kids throw each other with mud .-)

to post comments

Software suspend - again

Posted Feb 9, 2006 18:53 UTC (Thu) by khim (subscriber, #9252) [Link]

It would be so simple to just do two kconfig options for either suspend code and a 3rd for kexe/kdump/(kresume?)

If that's "so simple" then why did you never submit such patch to LKML ? Or have I missed it ? How big and intrusive was your patch ?

We have choice in many other places of the kernel (see schedulers), why not with the suspend code?

Guess. You know the basics:
1. If kernel developers can offer end-users choice without huge hassle they tend to do this.
2. They never offered such choice in regard to suspend code.
That's more then enough information to deduce correct answer...

Software suspend - again

Posted Feb 9, 2006 22:07 UTC (Thu) by NCunningham (guest, #6457) [Link]

>Sometimes the discussion is on a niveau where kids throw each other with
mud .-)

Yeah. I tried hard to avoid that, but don't think I was always successful.
Sorry for my contributions that were less than best in that regard.

Software suspend - again

Posted Feb 27, 2006 19:05 UTC (Mon) by Tv (guest, #7109) [Link]

> Why can't the kernel developers think of the kernel users fortune and just
> let _them_ decide?

Because kernel users won't maintain the code.