From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v4 0/5] Microblaze tune updates
Date: Tue, 4 Feb 2020 15:06:25 -0600 [thread overview]
Message-ID: <20200204210630.41960-1-mark.hatle@kernel.crashing.org> (raw)
Version 4 of the patch set.
I've collected all of the patches resently sent, and reworked them per
the comments on the mailing list.
The patches are directly available at:
git://git.openembedded.org/openembedded-core-contrib mgh/xilinx-microblaze
The work was broken up into a few more individual pieces. This will allow
backports to Zeus for fixes vs new features.
Mark Hatle (5):
microblaze tune: change microblazeeb to microblaze
microblaze tune: Allow no version to be set
microblaze tune: Enable 64-bit
microblaze tune: cleanup +=
Microblaze: Adjust Linux items from microblazeeb to microblaze
meta/classes/meson.bbclass | 2 +-
meta/classes/siteinfo.bbclass | 3 --
.../include/microblaze/arch-microblaze.inc | 35 ++++++++++++-------
.../microblaze/feature-microblaze-math.inc | 12 +++----
.../feature-microblaze-versions.inc | 4 +--
meta/lib/oe/elf.py | 3 --
.../{microblazeeb => microblaze}/objarch.h | 0
7 files changed, 31 insertions(+), 28 deletions(-)
rename meta/recipes-extended/ghostscript/ghostscript/{microblazeeb => microblaze}/objarch.h (100%)
--
2.17.1
next reply other threads:[~2020-02-04 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 21:06 Mark Hatle [this message]
2020-02-04 21:06 ` [PATCH v4 1/5] microblaze tune: change microblazeeb to microblaze Mark Hatle
2020-02-04 21:06 ` [PATCH v4 2/5] microblaze tune: Allow no version to be set Mark Hatle
2020-02-04 21:06 ` [PATCH v4 3/5] microblaze tune: Enable 64-bit Mark Hatle
2020-02-04 21:06 ` [PATCH v4 4/5] microblaze tune: cleanup += Mark Hatle
2020-02-04 21:06 ` [PATCH v4 5/5] Microblaze: Adjust Linux items from microblazeeb to microblaze Mark Hatle
2020-02-05 12:41 ` [PATCH v4 0/5] Microblaze tune updates Nathan Rossi
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=20200204210630.41960-1-mark.hatle@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@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.