Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/opencv3: python support needs .py modules
Date: Thu, 5 Sep 2019 20:49:02 +0200	[thread overview]
Message-ID: <20190905204902.127ebdaf@windsurf> (raw)
In-Reply-To: <20190905184403.19368-1-fontaine.fabrice@gmail.com>

Hello Fabrice,

On Thu,  5 Sep 2019 20:44:03 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Fixes:
>  - https://bugs.buildroot.org/show_bug.cgi?id=12171
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Thanks for the patch. A better commit log would be nice. But more
importantly, do we understand why it absolutely needs the .py file ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-09-05 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 18:44 [Buildroot] [PATCH 1/1] package/opencv3: python support needs .py modules Fabrice Fontaine
2019-09-05 18:49 ` Thomas Petazzoni [this message]
2019-09-05 18:55   ` Fabrice Fontaine
2019-09-08 15:48 ` Arnout Vandecappelle
2019-09-13 20:10   ` Thomas Petazzoni
2019-09-14 17:18     ` Arnout Vandecappelle
2019-09-15 20:52       ` Thomas Petazzoni

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=20190905204902.127ebdaf@windsurf \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox