All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
	"Eric Piel" <eric.piel@tremplin-utc.net>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	"Tony Lindgren" <tony@atomide.com>
Subject: Re: Driver lis3lv02d_i2c not working on Nokia RX-51
Date: Tue, 26 Mar 2013 09:08:08 -0700	[thread overview]
Message-ID: <CA+55aFwYvq5fZawbDVDPBu0ox2W7DQf5JmmyQHJYpBTOOTu_nQ@mail.gmail.com> (raw)
In-Reply-To: <20130326154442.GE18316@opensource.wolfsonmicro.com>

On Tue, Mar 26, 2013 at 8:44 AM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Mar 26, 2013 at 04:02:39PM +0100, Pali Rohár wrote:
>
>> What do you think how to fix this problem? I do not know about any
>> HW regulator for n900 accelerometer and possible solutions could
>> be revert that commit or adding fake regulator to board code...
>
> Reverting the fix is not an option, this is a clear bug in the platform.
>
> There will be a regulator here, the device needs power.

Bullshit.

This is a regression, and it needs to be fixed. The "device needs
power" crap is just that - crap. Nobody cares. OF COURSE all devices
need power, but that is totally irrelevant for a driver. The SSD in my
system "needs power", but I have absolutely zero regulator information
for it NOR DO I F*CKING NEED ANY!

Claiming that we need to know the power regulator for an accelerometer
is total utter idiocy and crap.

I'm going to revert that commit unless you can fix it some other way
(dummy regulators when you can't find a real one or whatever). The
notion that you have to have regulator information in order to use
some random device is insanity. I don't understand how you can even
start to make excuses like that. It's so obviously bogus that it's not
even funny.

Why do I have to explain the "no regressions" to long-time kernel
maintainers EVERY SINGLE RELEASE? What the f*ck is *wrong* with you
people? Seriously?

          Linus

  reply	other threads:[~2013-03-26 16:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16 23:46 Driver lis3lv02d_i2c not working on Nokia RX-51 Pali Rohár
2013-02-17 16:25 ` Mark Brown
2013-02-17 16:40   ` Pali Rohár
2013-02-17 18:17     ` Mark Brown
2013-03-24 14:50       ` Pali Rohár
2013-03-24 21:21         ` Mark Brown
2013-03-24 21:27           ` Pali Rohár
2013-03-24 22:14             ` Mark Brown
2013-03-24 22:44               ` Pali Rohár
2013-03-24 23:04                 ` Mark Brown
2013-03-26 15:02                   ` Pali Rohár
2013-03-26 15:44                     ` Mark Brown
2013-03-26 16:08                       ` Linus Torvalds [this message]
2013-03-26 17:08                         ` Mark Brown
2013-03-26 20:53                     ` Aaro Koskinen
2013-03-26 21:19                       ` Mark Brown
2013-03-28 14:11                       ` Pali Rohár

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=CA+55aFwYvq5fZawbDVDPBu0ox2W7DQf5JmmyQHJYpBTOOTu_nQ@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.