From: Andreas Mohr <andi@lisas.de>
To: Borislav Petkov <bp@alien8.de>, Andreas Mohr <andi@lisas.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Look Ma, da kernel is b0rken
Date: Wed, 5 Dec 2012 18:09:00 +0100 [thread overview]
Message-ID: <20121205170900.GA17276@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20121205164410.GD28556@liondog.tnic>
On Wed, Dec 05, 2012 at 05:44:10PM +0100, Borislav Petkov wrote:
> On Wed, Dec 05, 2012 at 05:39:05PM +0100, Andreas Mohr wrote:
> > Thanks to Borislav Petkov for his reply, too -
> > however I'd like to state that given this lack of tooling/attention
> > writing a mail in this more special manner was fully justified IMPHO.
>
> Ok, you've stated more than clearly that you're pissed with the current
> situation - I think we all got that.
Hohumm.
> Now, how do you suggest we change it constructively and how are you
> willing to help?
IMHO that's some common "misconception" - namely that innocent observing
by-standers are fully expected to get involved in the process.
Not necessarily, however (that's what domain experts are there for -
since people are well-advised to concentrate on the activities
that they are commonly involved with/do best).
I would be willing to handle corrections in the areas of drivers
I was working on (some corrections were already queued locally).
For scripted mechanisms (e.g. usefully nagging people as stated
in another posting), someone else would have to work on it I'm afraid.
Thanks,
Andreas Mohr
next prev parent reply other threads:[~2012-12-05 17:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 7:09 Look Ma, da kernel is b0rken Andreas Mohr
2012-12-05 14:29 ` Borislav Petkov
2012-12-05 15:27 ` Alan Cox
2012-12-05 15:31 ` Borislav Petkov
2012-12-05 15:47 ` Alan Cox
2012-12-05 15:59 ` Borislav Petkov
2012-12-05 17:04 ` Geert Uytterhoeven
2012-12-05 17:37 ` Borislav Petkov
2012-12-05 20:57 ` Stephen Rothwell
2012-12-05 21:12 ` Borislav Petkov
2012-12-05 21:41 ` Alan Cox
2012-12-05 21:46 ` Borislav Petkov
2012-12-05 21:39 ` Alan Cox
2012-12-05 21:38 ` Andrew Morton
2012-12-05 21:50 ` Borislav Petkov
2012-12-07 16:52 ` Andreas Mohr
2012-12-07 17:44 ` Borislav Petkov
2012-12-08 7:36 ` Andreas Mohr
2012-12-08 10:52 ` Borislav Petkov
2012-12-08 23:04 ` Alan Cox
2012-12-05 16:39 ` Andreas Mohr
2012-12-05 16:44 ` Borislav Petkov
2012-12-05 17:09 ` Andreas Mohr [this message]
2012-12-05 17:34 ` Borislav Petkov
2012-12-05 23:38 ` Rafael J. Wysocki
2012-12-05 23:35 ` Borislav Petkov
2012-12-06 14:04 ` Alan Cox
2012-12-06 20:56 ` Rafael J. Wysocki
2012-12-06 20:59 ` Borislav Petkov
2012-12-06 21:21 ` Rafael J. Wysocki
2012-12-06 21:20 ` Borislav Petkov
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=20121205170900.GA17276@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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