> Sorry. I misread your email. If the code looks like this: > > foo = kmalloc(); > if (!foo) > goto kmalloc_failed; > > The "kmalloc_failed" doesn't add any information. I find that this such a name approach would fit to your expectation of a source-oriented labeling of these identifiers. > We can see that kmalloc failed from the context. Which name pattern do you find more appropriate in such an use case? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
