A wonderful example of a company throwing code over the wall, watching it get rejected, and then running away as fast as possible, all the while yelling over their shoulder, "it's required on all new systems, you will love it!" We don't, it sucks, either fix it up, or I am removing it.
This is one example of linux kernel development being full of themselves. Yeah, sure thats one way to look at it. Another way would be "throw code over wall after spending time getting your boss to let you release the code and move on to what you are suppost to be working on before you get fired!!"
It take a lot of time and effort to convince your boss that releasing code to the linux community is a good thing but they don't want to pay you to work on a linux project when you have other stuff to do. If people like it or can use any of it then great if not ohh well.
To put it briefly, some of us don't work in the open source community or even use open source software at work so there is absolutely NO incentive for our boss to allow us to release anything let alone do continual work on it. Would be nicer if people would accept what it is and that is "hey, thanks for the example code, if someone is interested in working on that they can have a look at what you released"