From: "Bjørn Mork" <bjorn@mork.no>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [BISECTED 3.16-rc REGREGRESSION] backlight control stopped working
Date: Tue, 15 Jul 2014 09:33:13 +0200 [thread overview]
Message-ID: <87wqbfrs92.fsf@nemi.mork.no> (raw)
In-Reply-To: <53C4D17E.60206@redhat.com> (Hans de Goede's message of "Tue, 15 Jul 2014 09:00:14 +0200")
Hans de Goede <hdegoede@redhat.com> writes:
> It breaks things on exotic setups,
I find your attitude extremely arrogant. If you want to run a
non-exotic setup then you should definitely not consider Linux for your
desktop system...
I am trying to help you sort out a bug in code you have written, before
it hits a release. I do not really expect to receive a beer for this,
but maybe a little less of the "yes, I know there is a bug and I don't
give a damn" attitude.
Yes, I can of course fix *my* system, making your reported bug count go
from 1 to 0. Does that help you in any way? How does that make your
projected number of affected users change?
Bjørn
next prev parent reply other threads:[~2014-07-15 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 12:59 [BISECTED 3.16-rc REGREGRESSION] backlight control stopped working Bjørn Mork
2014-07-14 13:14 ` Hans de Goede
2014-07-14 13:27 ` Bjørn Mork
2014-07-14 16:24 ` Linus Torvalds
2014-07-14 16:59 ` Linus Torvalds
2014-07-14 20:45 ` Bjørn Mork
2014-07-14 20:49 ` Linus Torvalds
2014-07-14 21:46 ` Bjørn Mork
2014-07-14 22:19 ` Linus Torvalds
2014-07-14 18:01 ` Rafael J. Wysocki
2014-07-15 7:00 ` Hans de Goede
2014-07-15 7:33 ` Bjørn Mork [this message]
2014-07-15 10:59 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqbfrs92.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox