All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Zev Weiss <zweiss@equinix.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	"velumanit@hcl.com" <velumanit@hcl.com>,
	logananth hcl <logananth13.hcl@gmail.com>
Subject: Re: Procedure for the send review on u-boot patch
Date: Fri, 14 Jan 2022 16:21:07 -0600	[thread overview]
Message-ID: <YeH3UzT4uAwauF7s@heinlein> (raw)
In-Reply-To: <20220114220239.GH5754@packtop>

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

On Fri, Jan 14, 2022 at 10:02:40PM +0000, Zev Weiss wrote:
> On Fri, Jan 14, 2022 at 10:45:50AM PST, Patrick Williams wrote:

> >```
> >$ git grep "v2019.04"
> >meta-aspeed/recipes-bsp/u-boot/u-boot-common-aspeed-sdk_2019.04.inc:PV = "v2019.04+git${SRCPV}"
> >```
> >
> >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.
> >
> 
> I think g200a, fp5280g2, and vegman are all using the new branch?  And
> if I'm interpreting the below correctly, also any aspeed-g6 systems that
> haven't overridden the defaults?

Thanks, my git-grep failed me and for some reason I thought 'sdk' means
something else w.r.t. u-boot.  You appear to be correct.

Logananth, we might want to upgrade Yv2/Tiogapass to this newer branch if
possible then.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-01-14 22:21 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 [this message]
2022-01-17  5:36     ` Lei Yu
2022-01-17  6:54     ` Joel Stanley
2022-01-17 12:00       ` Joel Stanley
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=YeH3UzT4uAwauF7s@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=logananth13.hcl@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=velumanit@hcl.com \
    --cc=zweiss@equinix.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.