All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] kmsxx: new package
Date: Wed, 8 Jun 2016 21:57:45 +0200	[thread overview]
Message-ID: <20160608215745.0994dd60@free-electrons.com> (raw)
In-Reply-To: <20160608190424.GK14179@lukather>

Hello,

On Wed, 8 Jun 2016 21:04:24 +0200, Maxime Ripard wrote:

> Honestly, I don't care at all about the python bindings.
> 
> I'll remove support for that in the v3, and if anyone is ever
> interested in adding support for it, he'll work on it (and things will
> have settled down hopefully)

FWIW: I discussed this topic with Maxime today. I very much prefer
having a basic kmsxx package merged, with the features that Maxime
uses/needs, rather than waiting endlessly to resolve all the Python
bindings issues. So let's merge a simpler version of kmsxx that doesn't
have the Python bindings, and when someone is interested enough to have
the Python bindings, this someone can submit follow-up patches.

So, yes, Maxime: please send a simpler version of the patch.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-06-08 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  8:38 [Buildroot] [PATCH v2] kmsxx: new package Maxime Ripard
2016-06-02  7:17 ` Maxime Ripard
2016-06-08 10:11   ` Yegor Yefremov
     [not found]     ` <91587869.72Lxhe2Mek@avalon>
2016-06-08 10:27       ` Yegor Yefremov
     [not found]         ` <146541087.IVqEMkkuFm@avalon>
2016-06-08 14:19           ` Yegor Yefremov
2016-06-08 14:34             ` Yegor Yefremov
2016-06-08 19:04               ` Maxime Ripard
2016-06-08 19:57                 ` Thomas Petazzoni [this message]

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=20160608215745.0994dd60@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.