mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	Djalal Harouni <tixxdz@opendz.org>,
	"systemd-devel\@lists.freedesktop.org" 
	<systemd-devel@lists.freedesktop.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Havoc Pennington <havoc.pennington@gmail.com>
Subject: Re: kdbus refactoring?
Date: Mon, 09 Nov 2015 17:14:34 +0000	[thread overview]
Message-ID: <yw1xd1vj5c3p.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <20151109170750.GA25306@kroah.com> (Greg KH's message of "Mon, 9 Nov 2015 09:07:50 -0800")

Greg KH <gregkh@linuxfoundation.org> writes:

> On Mon, Nov 09, 2015 at 05:02:45PM +0000, Måns Rullgård wrote:
>> Andy Lutomirski <luto@amacapital.net> writes:
>> 
>> > On Sun, Nov 8, 2015 at 3:30 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> >> On Sun, Nov 08, 2015 at 10:39:43PM +0100, Richard Weinberger wrote:
>> >>> On Sun, Nov 8, 2015 at 10:35 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> >>> > On Sun, Nov 08, 2015 at 10:06:31PM +0100, Richard Weinberger wrote:
>> >>> >> Hi all,
>> >>> >>
>> >>> >> after reading on the removal of kdbus from Rawhide[1] I've searched
>> >>> >> the mailinglist archives for more details but didn't find anything.
>> >>> >> So, what are your plans?
>> >>> >>
>> >>> >> [1] https://lists.fedoraproject.org/pipermail/kernel/2015-October/006011.html
>> >>> >
>> >>> > As that link said, based on the result of the code being in Rawhide, it
>> >>> > is now being reworked / redesigned.  The result will be posted for
>> >>> > review "when it's ready".
>> >>>
>> >>> If you rework/redesign something you have to know what you want to change.
>> >>> That's why I was asking for the plan...
>> >>
>> >> Since when do people post "plans" or "design documents" on lkml without
>> >> real code?  Again, code will be posted when it's ready, like any other
>> >> kernel submission.
>> >
>> > I ask for feedback on ideas and designs on a fairly regular basis.  I
>> > even frequently get valuable feedback :)
>> >
>> > I would like to think that the kernel community would have something
>> > of value to add to the process of designing and implementing a major
>> > new IPC mechanism.
>> 
>> The "trust us, we'll show it when it's ready" attitude reminds me of the
>> controversial TPP and TTIP negotiations.
>
> Ok, that's just trolling, cut it out.
>
> When something is even in the "hey look, it works, here's the big
> changes from last time", we will of course post it, but right now,
> things are being totally revisited based on the feedback we have
> received so far.  Give people a chance to recover from conferences and
> then get back to work...

If there are public discussions about it elsewhere, you could have
simply pointed at those instead being condescending.

-- 
Måns Rullgård
mans@mansr.com

  reply	other threads:[~2015-11-09 17:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08 21:06 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
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 [this message]
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=yw1xd1vj5c3p.fsf@unicorn.mansr.com \
    --to=mans@mansr.com \
    --cc=ebiederm@xmission.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=havoc.pennington@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=systemd-devel@lists.freedesktop.org \
    --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

all inboxes | Powered by JetHome®