Comment 95 for bug 1258837

On Friday 02 January 2015 11:56:09 Christopher M. Penalver wrote:
> Rob:
> >"So what I'm doing is more purposeful than nagging people
> >about opening a new bug report with info that you already
> >have."
>
> Spamming everyone with comments about a forum post is not
> helping here. As well, nobody has the information previously
> requested from you, as you didn't file a new report.
>

Christopher, spamming everyone without your useless posts about
duplicating same bug is even less useless.

> >"*IF* it is a BIOS/firmware/EC bug there is no point in
> >opening yet another bug report for an issue that can't be
> >resolved in Linux!"
>
> Then you don't understand how linux kernel development works.

And you Christopher do not know how linux kernel development
works too! *NOBODY* in linux kernel development want from users
to open duplicate bug reports.

> On select occasions, linux kernel engineers (not Dell
> employees) have implemented patches that WORKAROUND buggy,
> and outdated BIOS and hardware firmware.
>

Citation needed (TM). Who and how implemented WORKAROUND for
outdated BIOS? And what is outdated BIOS??

Btw, *I* am that developer who implemented WORKAROUND for current
situation and sent patch to upstream kernel (which is now part of
3.18 release). But it has nothing with BIOS and there are no
outdated BIOS versions. If you still do not understand this
problem reported in this (and more other!) bugs happens on all
Latitude Exx40 machines with any BIOS version.

I'm fed up with you. You just spam bug reports, bitching on users
who reported serious and critical problems, you did not helped
with *anything* and also you did not implemented any fix for this
problem.

Sorry but *all* your comments in this (and others too) are
totally useless. It did not helped me or other people who wanted
to fix this problem.

What you have done is just fed up users and forced them to not
report bugs anymore because it is useless...

> However, by not filing a report, you are robbing developers to
> track the true impact this has, all the hardware permutations
> that may be affected, and the opportunity to review your
> hardware specifically (marking yourself affected, or making
> "Me too!" comments is useless here as it's not verifiable by
> anyone). As well, you are just adding comment noise that
> isn't contributing towards having the issue addressed. By not
> doing as previously requested, you are only delaying your own
> problem from being addressed.

Addressed to whom? In last year nobody else provided any fix for
this bug. So what are you trying to do? We already know that this
problem is *same* for all Exx40 laptops and affect all people.
And posts "me too" just say that this problem happens really on
all those laptops and with all BIOS versions.

--
Pali Rohár
<email address hidden>