All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	velumanit@hcl.com, logananth hcl <logananth13.hcl@gmail.com>
Subject: Re: Procedure for the send review on u-boot patch
Date: Mon, 17 Jan 2022 12:00:46 +0000	[thread overview]
Message-ID: <CACPK8Xdxzxasoo8onu1QbPXFRYr8+saHAg32bZdpp9d7KH2CJQ@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XebyrX1jpiJxsvH7+kJxKYMWgbWG7GZYi9BU9qYJWHi6w@mail.gmail.com>

On Mon, 17 Jan 2022 at 06:54, Joel Stanley <joel@jms.id.au> wrote:

> > I think everyone doing AST2400/AST2500 work has been copying from existing
> > systems and still pointing to the v2016.07 branch that we have working in the
> > tree.
>
> Where possible I review for this. If there's a way for gerrit to tell
> me when a new machine is added I'd enforce it more often.
>
> I've mentioned on the list before that I'd welcome a change that flips
> the default to the new tree. That would require setting
> PREFERRED_PROVIDER_u-boot for all existing aspeed 2400/2500 machines
> that don't have it set, and then changing meta-aspeed.

I've given this a go:

https://gerrit.openbmc-project.xyz/q/topic:aspeed-u-boot-default

I did some boot tests of yosemitev2 and romulus in qemu and all looked fine.

Next step would be to convert the EVB to the new u-boot, and perhaps
some of the prominent machines that people use to base their new
systems, on so they start on the right track.

  reply	other threads:[~2022-01-17 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  8:52 Procedure for the send review on u-boot patch logananth hcl
2022-01-13 22:40 ` Joel Stanley
2022-01-14 18:45   ` Patrick Williams
2022-01-14 22:02     ` Zev Weiss
2022-01-14 22:21       ` Patrick Williams
2022-01-17  5:36     ` Lei Yu
2022-01-17  6:54     ` Joel Stanley
2022-01-17 12:00       ` Joel Stanley [this message]
2022-01-18 17:40       ` Patrick Williams
2022-01-19  3:06         ` Joel Stanley

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=CACPK8Xdxzxasoo8onu1QbPXFRYr8+saHAg32bZdpp9d7KH2CJQ@mail.gmail.com \
    --to=joel@jms.id.au \
    --cc=logananth13.hcl@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    --cc=velumanit@hcl.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 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.