public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: David Herrmann <dh.herrmann@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Djalal Harouni <tixxdz@opendz.org>,
	Havoc Pennington <havoc.pennington@gmail.com>
Subject: Re: kdbus refactoring?
Date: Mon, 9 Nov 2015 16:55:57 +0100	[thread overview]
Message-ID: <5640C20D.8000009@nod.at> (raw)
In-Reply-To: <20151109150249.GA8745@kroah.com>

Am 09.11.2015 um 16:02 schrieb Greg KH:
> On Mon, Nov 09, 2015 at 10:28:42AM +0100, Richard Weinberger wrote:
>> Am 09.11.2015 um 10:19 schrieb David Herrmann:
>>> On Mon, Nov 9, 2015 at 10:14 AM, Peter Zijlstra <peterz@infradead.org> wrote:
>>>> On Mon, Nov 09, 2015 at 09:56:04AM +0100, David Herrmann wrote:
>>>>
>>>>> The submission and following year of development followed the 'kernel
>>>>> way'.
>>>>
>>>> This is not true; the last complete posting I could find was:
>>>>
>>>>   Date: Mon,  9 Mar 2015 14:09:06 +0100
>>>>   Subject: [PATCH v4 00/14] Add kdbus implementation
>>>
>>> ..which was the last time we proposed it for inclusion.
>>
>> Guys, let's cool down. :-)
>>
>> What Peter is complaining about is that since the last proposal a lot
>> of iterative patches and even pull requests were sent instead of
>> complete patch series.
>> The expectation was that you send patch series with fixes folded in
>> as long the review takes.
> 
> And that will happen, when the code is ready, nothing different is
> happening here from any other code submission.  I don't know why people
> somehow think we don't know how to do this whole thing, it's as if they
> don't trust us, which is sad.

Well, what me makes sad is that my little question ended up in a flame.
If someone asks me how I plan to solve something I'm become proud and tell my ideas.
All I got was rejection and platitudes.

Thanks,
//richard

  reply	other threads:[~2015-11-09 15:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08 21:06 kdbus refactoring? Richard Weinberger
2015-11-08 21:35 ` Greg KH
2015-11-08 21:39   ` Richard Weinberger
2015-11-08 23:30     ` Greg KH
2015-11-09  0:53       ` Josh Triplett
2015-11-09  8:34         ` David Herrmann
2015-11-09  8:37           ` Richard Weinberger
2015-11-09  8:48           ` Peter Zijlstra
2015-11-09  8:56             ` David Herrmann
2015-11-09  9:08               ` Borislav Petkov
2015-11-09  9:14               ` Peter Zijlstra
2015-11-09  9:19                 ` David Herrmann
2015-11-09  9:28                   ` Richard Weinberger
2015-11-09 15:02                     ` Greg KH
2015-11-09 15:55                       ` Richard Weinberger [this message]
2015-11-09  8:15       ` Richard Weinberger
2015-11-09 16:51       ` Andy Lutomirski
2015-11-09 17:02         ` Måns Rullgård
2015-11-09 17:07           ` Greg KH
2015-11-09 17:14             ` Måns Rullgård
2015-11-09 17:23             ` Andy Lutomirski
2015-11-12  5:35               ` Kalle A. Sandstrom

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=5640C20D.8000009@nod.at \
    --to=richard@nod.at \
    --cc=dh.herrmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=havoc.pennington@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=richard.weinberger@gmail.com \
    --cc=tixxdz@opendz.org \
    --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