![]() | |||||||||||||
Messages in this thread |
In article <20020921112245.27021.qmail@unibar> you wrote: > This patch cleans up the __FUNCTION__ pasting to the new > standard. is this normal, that we dont have a rate limit in those functions? And even worse, that there is no error handling like signalling this back to the channel? In this case this looks especially annoying, since it is a state changing event, if when lost may totally screw up the state engine (if i understand the comment "Send event (connection, disconnection, etc) to X.25 socket layer" right. Greetings Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:29 [W:0.036 / U:0.350 seconds] ©2003-2008 Jasper Spaans | |||||||||||||