All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Rossi <nathan@nathanrossi.com>
To: Mark Hatle <mark.hatle@kernel.crashing.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4 0/5] Microblaze tune updates
Date: Wed, 5 Feb 2020 22:41:34 +1000	[thread overview]
Message-ID: <CA+aJhH2WTqiXEDBj7nSHiPQ9CeY2eF=aG_Vd+xJ=XpJx-o0Peg@mail.gmail.com> (raw)
In-Reply-To: <20200204210630.41960-1-mark.hatle@kernel.crashing.org>

On Wed, 5 Feb 2020 at 07:06, Mark Hatle <mark.hatle@kernel.crashing.org> wrote:
>
> 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

Looks good. I gave it a quick test, qemu big endian builds and boots
core-image-minimal now.

Thanks,
Nathan


      parent reply	other threads:[~2020-02-05 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 21:06 [PATCH v4 0/5] Microblaze tune updates Mark Hatle
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 ` Nathan Rossi [this message]

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='CA+aJhH2WTqiXEDBj7nSHiPQ9CeY2eF=aG_Vd+xJ=XpJx-o0Peg@mail.gmail.com' \
    --to=nathan@nathanrossi.com \
    --cc=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.