Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8 0/5] package/python-scipy: new package
Date: Tue, 7 Apr 2020 17:01:11 +0200	[thread overview]
Message-ID: <20200407150111.GP22325@scaer> (raw)
In-Reply-To: <CAMty3ZCQ8qmZY9f=Lqv71fMYX3ej1eDxvL00w42B9fxSsagmjA@mail.gmail.com>

Jagan, All,

On 2020-04-07 19:13 +0530, Jagan Teki spake thusly:
> On Tue, Apr 7, 2020 at 5:19 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> > On Tue,  7 Apr 2020 16:45:10 +0530
> > Jagan Teki <jagan@amarulasolutions.com> wrote:
> > > This is v8 changes for python-scipy, here is the previous
> > > version series[1].
> > Thanks for this new iteration. Could you have a look at the backlog of
> > patches at http://patchwork.ozlabs.org/project/buildroot/list/ and
> > update any patch that is no longer relevant due to this new iteration
> > to the state "Superseded" ? You can do that yourself for the patches
> > that you have sent (provided that you have a patchwork account matching
> > the e-mail used to send the patches). For the other patches, you can
> > simply let us know, and we'll update the patch status.
> >
> > This helps us keep a patchwork backlog that makes sense.
> 
> Yes, I've updated all my previous version changes. regarding pybind11,
> adam has this series [2]. I already incorporated test patch in my
> series as per his request.
> [2] http://patchwork.ozlabs.org/project/buildroot/list/?series=145831

So I've marked the seriers from Adam as superseded.

However, there was a review of his pybind11 patch: since it installs
only a header, it should be _INSTALL_TARGET = NO

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2020-04-07 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 11:15 [Buildroot] [PATCH v8 0/5] package/python-scipy: new package Jagan Teki
2020-04-07 11:15 ` [Buildroot] [PATCH v8 1/5] package/python-numpy: Bump to version 1.18.2 Jagan Teki
2020-05-01 12:37   ` Thomas Petazzoni
2020-04-07 11:15 ` [Buildroot] [PATCH v8 2/5] package/python-numpy: fixup npymath.ini for numpy extensions Jagan Teki
2022-01-07 22:10   ` Arnout Vandecappelle
2020-04-07 11:15 ` [Buildroot] [PATCH v8 3/5] package/python-pybind11: new host package Jagan Teki
2020-04-07 11:15 ` [Buildroot] [PATCH v8 4/5] support/testing: add python-pybind11 test Jagan Teki
2022-01-07 21:38   ` Arnout Vandecappelle
2020-04-07 11:15 ` [Buildroot] [PATCH v8 5/5] package/python-scipy: new package Jagan Teki
2022-01-07 23:12   ` Arnout Vandecappelle
2020-04-07 11:49 ` [Buildroot] [PATCH v8 0/5] " Thomas Petazzoni
2020-04-07 13:43   ` Jagan Teki
2020-04-07 15:01     ` Yann E. MORIN [this message]
2020-04-07 16:18       ` Jagan Teki
2020-07-03  8:09         ` Jagan Teki

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=20200407150111.GP22325@scaer \
    --to=yann.morin.1998@free.fr \
    --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