From: Martin Steigerwald <martin@lichtvoll.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andy Lutomirski <luto@amacapital.net>,
Richard Weinberger <richard.weinberger@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Herrmann <dh.herrmann@gmail.com>,
Djalal Harouni <tixxdz@opendz.org>,
Havoc Pennington <havoc.pennington@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Tom Gundersen <teg@jklm.no>, Daniel Mack <daniel@zonque.org>
Subject: Re: kdbus: to merge or not to merge?
Date: Thu, 25 Jun 2015 08:05:58 +0200 [thread overview]
Message-ID: <5286070.NYrIjcpPS3@merkaba> (raw)
In-Reply-To: <20829057.evLRBZOrmM@merkaba>
Am Donnerstag, 25. Juni 2015, 08:01:35 schrieb Martin Steigerwald:
> Am Mittwoch, 24. Juni 2015, 19:20:27 schrieb Linus Torvalds:
> > On Wed, Jun 24, 2015 at 7:14 PM, Steven Rostedt <rostedt@goodmis.org>
>
> wrote:
> > > I don't think it will complicate things even if the API changes. The
> > > distros will have to deal with that fall out. Mainline only cares
> > > about
> > > its own regressions. But any API changes would only be done for good
> > > reasons, and give the distros an excuse to fix whatever was done wrong
> > > in the first place.
> >
> > I don't think that's true.
> >
> > Realistically, every single kernel developer tends to work on a
> > machine with some random distro. If that developer cannot compile his
> > own kernel because his distro stops working, or has to use some
> > "kdbus=0" switch to turn off the kernel kdbus and (hopefuly) the
> > distro just switches to the legacy user mode bus, then for that
> > developer, merging and enabling incompatible kdbus implementation is
> > basically a regression.
> >
> > We've seen this before. We end up stuck with the ABI of whatever user
> > land applications. It doesn't matter where that ABI came from.
> >
> > I do agree that distro's that want to enable kdbus before any agreed
> > version has been merged would get to also act as guinea pigs and do
> > their own QA, and handle fallout from whatever problems they encounter
> > etc. That part might be good. But I don't think we really end up
> > having the option to make up some incompatible kdbus ABI
> > after-the-fact.
>
> Linus, so is that a recommendation to the distros to be careful to put
> kdbus into the distro kernel right now and probably better defer it or
> are you thinking that the ABI of kdbus already is suitable for merging
> and you see no issues to merge a kdbus with the ABI it currently has, but
> probably otherwise improved?
Or, do you think, that there is a different option to handle this then the
both I outlined above?
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2015-06-25 6:06 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 6:06 kdbus: to merge or not to merge? Andy Lutomirski
2015-06-23 6:31 ` Andy Lutomirski
2015-06-23 6:41 ` Greg KH
2015-06-23 7:22 ` Richard Weinberger
2015-06-23 9:25 ` Martin Steigerwald
2015-06-23 9:38 ` Martin Steigerwald
2015-06-23 15:07 ` Andy Lutomirski
2015-06-25 2:14 ` Steven Rostedt
2015-06-25 2:20 ` Linus Torvalds
2015-06-25 6:01 ` Martin Steigerwald
2015-06-25 6:05 ` Martin Steigerwald [this message]
2015-06-25 13:34 ` Theodore Ts'o
2015-06-25 14:03 ` Martin Steigerwald
2015-06-23 9:12 ` Borislav Petkov
2015-07-08 13:54 ` Pavel Machek
2015-07-09 8:39 ` Geert Uytterhoeven
2015-07-09 10:29 ` Joe Perches
2015-07-09 10:57 ` Geert Uytterhoeven
2015-07-09 11:36 ` Pavel Machek
2015-06-23 23:19 ` Linus Torvalds
2015-06-24 0:52 ` Andy Lutomirski
2015-06-24 8:05 ` Ingo Molnar
2015-06-24 10:41 ` Eric W. Biederman
2015-06-24 10:46 ` Martin Steigerwald
2015-06-24 13:18 ` Ingo Molnar
2015-06-24 17:39 ` David Lang
2015-06-24 18:41 ` Eric W. Biederman
2015-06-24 18:50 ` Martin Steigerwald
2015-06-24 19:12 ` David Lang
2015-06-25 7:57 ` Geert Uytterhoeven
2015-06-25 15:26 ` Steven Rostedt
2015-06-25 6:31 ` Greg KH
2015-06-25 6:48 ` David Lang
2015-06-25 7:47 ` Ingo Molnar
2015-06-25 7:51 ` Ingo Molnar
2015-06-24 11:43 ` Martin Steigerwald
2015-06-24 13:27 ` Ingo Molnar
2015-06-24 9:55 ` Alexander Larsson
2015-06-24 14:38 ` Andy Lutomirski
[not found] ` <CAHr-LrYWNwv6_YLoP-B3duQ1QsjPiTiaEnjBQ7j2brPMeTgA3A@mail.gmail.com>
[not found] ` <CALCETrW3F6YP_H1oRJa47f1DT7B35OubhJYSnq0U-_GmFQHNOA@mail.gmail.com>
2015-06-24 17:11 ` Alexander Larsson
2015-06-24 19:43 ` Andy Lutomirski
2015-06-24 20:45 ` Alexander Larsson
2015-08-03 23:02 ` Andy Lutomirski
2015-08-04 8:58 ` David Herrmann
2015-08-04 13:46 ` Linus Torvalds
2015-08-04 14:09 ` David Herrmann
2015-08-04 14:47 ` Andy Lutomirski
2015-08-05 0:18 ` Andy Lutomirski
2015-08-06 7:06 ` Daniel Mack
2015-08-06 15:27 ` Andy Lutomirski
2015-08-06 17:24 ` Daniel Mack
2015-08-05 7:10 ` David Herrmann
2015-08-05 20:11 ` Andy Lutomirski
2015-08-06 8:04 ` David Herrmann
2015-08-06 8:25 ` Martin Steigerwald
2015-08-06 15:21 ` Andy Lutomirski
2015-08-06 18:14 ` Daniel Mack
2015-08-06 18:43 ` Andy Lutomirski
2015-08-07 14:40 ` Daniel Mack
2015-08-07 15:09 ` Andy Lutomirski
[not found] ` <CA+55aFxDLt-5+=xXeYG4nJKMb8L_iD9FmwTZ2VuughBku-mW3g@mail.gmail.com>
2015-08-09 19:00 ` Greg Kroah-Hartman
2015-08-09 22:11 ` Daniel Mack
2015-08-10 2:10 ` Andy Lutomirski
2015-08-10 17:04 ` Linus Torvalds
2015-08-10 2:48 ` David Lang
2015-08-07 15:37 ` cee1
-- strict thread matches above, loose matches on Subject: below --
2015-07-01 0:03 Kalle A. Sandstrom
2015-07-01 16:51 ` David Herrmann
2015-07-06 21:18 ` 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=5286070.NYrIjcpPS3@merkaba \
--to=martin@lichtvoll.de \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.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=richard.weinberger@gmail.com \
--cc=rostedt@goodmis.org \
--cc=teg@jklm.no \
--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