 Linux is the kernel and Android has a little tiny patches to the Linux kernel. Just like any other any Linux product has a few patches. But it's not the part of the mainline because that kernel was appreciated from the main tree and they're maintaining separately. But that's what any any embedded product almost always you can't ship a main kernel because it's the last one released, you have a product, you have special hardware support. Now Google for the Android platform made some changes to it to support the power management model that they wanted, which is a very valid model and so that made things a little different. They do some core changes that aren't in the mainline kernel. That being said we have worked really hard and worked with them to try and make that acceptable and one result of the kernel summit two days ago is we're definitely going to revisit that and there really is no reason why we shouldn't be taking that. And these are very tiny bits of code so to call it a fork. That's why the reason I am because there is a lot of misinformation out there. There is a lot of misinformation. That is why whatever it is, if it is addressed properly it just goes away. The problem with Android, it's not a problem, the difference with Android from a traditional embedded product is they are creating a partner ecosystem so that people rely on them. So in order to build another product you have to go grab the patches from them first and integrate stuff. Otherwise, if you look at the stuff, the long term consumer electronics kernel initiative, that's to help address those issues that all these companies are doing the same back porting and same patch work on their own, that's all contributed together and making it one spot and that's going to do that. It's helpful that Android patches in because everybody is relying on them and because of that it's going to go upstream.