[watwut]

Those were not delivered fixes, that was work in progress that is still work in progress. And the dude who was "called out" works for Amazon.

[mrmondo]

FYI - The “dude” from Amazon worked for Intel for 8 years before joining Amazon UK just over a year ago.

[numbsafari]

The “dude” is also probably working under an insane amount of pressure and being made to feel like he is somehow responsible or at fault for the whole situation. Best not to make it personal from the peanut gallery.

[sundarurfriend]

> Best not to make it personal from the peanut gallery.

That's a very uncharitable interpretation of your parent comment, which was simply pointing out his connection and history with Intel.

[FPGAhacker]

Are you sure it is not you that has made the uncharitable interpretation?

I read the peanut gallery comment as an agreement that the guy knows what he’s talking about.

[mrmondo]

FWIW - I took it as a somewhat rude reply but hey it’s the internet so no big deal.

[mrmondo]

I did not, and do not lay any blame, I only provided context to the prior comment.

[SmellyGeekBoy]

So the person supposedly single-handedly working on this fix doesn't even work for Intel? That strikes me as... Odd?

[watwut]

Where did you got single-handedly from? Of course multiple people cooperate on those patches. That is it was possible for Linus Torwalds to join their discussion, it would all be much less public if only one institution or person worked on it.

[cornholio]

So what you are saying is that Intel didn't bother to support Linux even with a crappy fix, like they did for Microsoft? Good to hear the Chinese are well supported though.

[watwut]

That is not what I said and not what situation implied. In situation where you have like zero factual information you went out of your way to make up most damaging possibility you could have.