All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] ne10: set NE10_TARGET_ARCH with an override instead of anonymous python
Date: Fri, 26 Apr 2019 22:34:00 +0200	[thread overview]
Message-ID: <CALbNGRS7ceuKHHZL-EZ6VcprbpXUFS8k7coeVL9RKQMT2G_7hw@mail.gmail.com> (raw)
In-Reply-To: <CA+chaQfZE7kZHown5xfxZQf+yQoB_iqtuH=LFKJhhoqJ7tVF0w@mail.gmail.com>

On Fri, Apr 26, 2019 at 9:27 PM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> I'm not using ne10 or libopus anywhere, it was just breaking
> sstate-diff-machines.sh script by adding that unjustifiable dependency
> based on TUNE_FEATURES.
>
> I was going to send v2 with the armv7ve entries as requested by Andreas (I
> forgot that armv7ve tunes no longer include armv7a in overrides), but if
> someone wants to rework it to test for neon in TUNE_FEATURES feel free to
> do so.
>
> It didn't check for neon before, so at least this change didn't make it
> worse.
Yeah - you fix something you are not interested in and people (either
not using it) open up wishlists..

Thanks (and sorry :)

Andreas


  reply	other threads:[~2019-04-26 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 19:00 [meta-oe][PATCH] ne10: set NE10_TARGET_ARCH with an override instead of anonymous python Martin Jansa
2019-04-25 21:14 ` Andreas Müller
2019-04-26  5:20 ` Adrian Bunk
2019-04-26 17:35   ` Khem Raj
2019-04-26 19:27     ` Martin Jansa
2019-04-26 20:34       ` Andreas Müller [this message]
2019-05-22 22:16         ` Andre McCurdy
2019-05-22 23:28           ` [meta-oe][PATCH] ne10, libopus: add armv7ve override as well Martin Jansa

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=CALbNGRS7ceuKHHZL-EZ6VcprbpXUFS8k7coeVL9RKQMT2G_7hw@mail.gmail.com \
    --to=schnitzeltony@gmail.com \
    --cc=bunk@stusta.de \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 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.