I looked at the kernelbug-conversation, about this and it seems that they just removed the message. Seemingly, the don't think that this is causing any problems.
------- Comment #7 From Andrew Morton 2007-08-02 15:40:09 [reply] -------
Greg, could you please consider removing that message, or rephrasing it
in some manner so that it is less alarming?
------- Comment #8 From Greg Kroah-Hartman 2007-10-03 16:03:29 [reply] -------
The message is now gone in 2.6.23. Closing this bug.
Well, I'm not so sure about this, but I'll notice it when I use the next kernel-release.
Hello,
I looked at the kernelbug- conversation, about this and it seems that they just removed the message. Seemingly, the don't think that this is causing any problems.
------- Comment #7 From Andrew Morton 2007-08-02 15:40:09 [reply] -------
Greg, could you please consider removing that message, or rephrasing it
in some manner so that it is less alarming?
------- Comment #8 From Greg Kroah-Hartman 2007-10-03 16:03:29 [reply] -------
The message is now gone in 2.6.23. Closing this bug.
Well, I'm not so sure about this, but I'll notice it when I use the next kernel-release.
Greetings,
Michel