> Don't worry, you're not the only one TIred here... Grrr. I'm in no mood to take any TI puns right now. That was unwarranted. > > > So here's the quick mail you want: > > "I may or may not be able to clean up this driver in the near future. Felipe > > Balbi graciously agress to do it for us. So I am pleased to announce he will > > clean up this driver and send it upstream. If he needs any help with this, I > > will try to provide it to him (or anyone else for that matter) on a best-effort > > basis. Good luck." > > > > > > > > > > Anyways, I'll keep going with my cleanups and when I get a platform to > > > test ehci, I'll try to test the patches and keep going with the > > > workarounds. > > > > If you want help with testing, I can give it to you. If not, you can test > > it yourself - I couldn't care less. > > And you want me to agree with it ? I really was hoping we could work > together with TI but seems I'm the only one who still believes in that. I made that offer - so there is at least one other believer of working together. You're the one that wants to do this on your own - and I'm okay with that. > > As you said yourself, you couldn't care less right ? You couldn't care > less if the driver works or not, you couldn't care less if we have good > omap support out of mainline kernel, you couldn't care less if the > driver is readable or not, etc etc etc. That's not true. I do care. It __is__ important to me that OMAP support goes to mainline. And I do not like it that it hasn't happened yet. Sorry. What happened with EHCI here is kind of similar to what you've done with MUSB patches recently anyway. > I imagine if all of us would be > taking the same behavior as you are... I don't understand what you mean, but I'm guessing it doesn't matter. > > Well, I'm not here to flood the list discussing this kinds of > issues with you. Standard behavior for you. That's the way you end all discussions that go beyond 5 mails!-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
