From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/6] arch-armv8a.inc: add tune include for armv8
Date: Tue, 05 Feb 2019 15:12:36 +0000 [thread overview]
Message-ID: <c063995d478bf52b08936f2e70caa754d30f97ba.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190205025727.1937-1-raj.khem@gmail.com>
On Mon, 2019-02-04 at 18:57 -0800, Khem Raj wrote:
> From: ayaka <ayaka@soulik.info>
>
> There are some addtional instructions apart from bare armv8,
> also there is armv8.1, armv8.2.
>
> Most the processor would support crc, except X-gene 1.
>
> Signed-off-by: Randy Li <ayaka@soulik.info>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/conf/machine/include/arm/arch-armv8.inc | 1 -
> meta/conf/machine/include/arm/arch-armv8a.inc | 28
> +++++++++++++++++++
> 2 files changed, 28 insertions(+), 1 deletion(-)
> delete mode 100644 meta/conf/machine/include/arm/arch-armv8.inc
> create mode 100644 meta/conf/machine/include/arm/arch-armv8a.inc
Renaming the file when other things use it causes failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/256/steps/7/logs/step1c
Cheers,
Richard
next prev parent reply other threads:[~2019-02-05 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 2:57 [PATCH 1/6] arch-armv8a.inc: add tune include for armv8 Khem Raj
2019-02-05 2:57 ` [PATCH 2/6] ThunderX: update the armv8a rules Khem Raj
2019-02-05 2:57 ` [PATCH 3/6] tune-cortexa32: add tunes for ARM Cortex-A32 Khem Raj
2019-02-05 2:57 ` [PATCH 4/6] tune-cortexa35: add tunes for ARM Cortex-A35 Khem Raj
2019-02-05 2:57 ` [PATCH 5/6] tune-cortexa53: add tunes for ARM Cortex-A53 Khem Raj
2019-02-05 2:57 ` [PATCH 6/6] tune-cortexa72: add tunes for ARM Cortex-A72 Khem Raj
2019-02-05 15:12 ` Richard Purdie [this message]
2019-02-05 15:57 ` [PATCH 1/6] arch-armv8a.inc: add tune include for armv8 Khem Raj
2019-02-05 15:57 ` akuster808
2019-02-05 17:37 ` Khem Raj
2019-02-23 19:37 ` Mike Crowe
2019-02-23 20:04 ` Khem Raj
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=c063995d478bf52b08936f2e70caa754d30f97ba.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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