All of lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Lee <troy_lee@aspeedtech.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Thang Nguyen <thang@os.amperecomputing.com>
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
Date: Thu, 11 Mar 2021 03:11:07 +0000	[thread overview]
Message-ID: <20210311031107.GA2095174@aspeedtech.com> (raw)
In-Reply-To: <20210309221020.ut4gds26ivcp6mst@thinkpad.fuzziesquirrel.com>

Hi Brad,

The 03/10/2021 06:10, Brad Bishop wrote:
> On Mon, Mar 08, 2021 at 12:52:41PM +0700, Thang Nguyen wrote:
> >Hi,
> >
> >On 05/02/2021 09:27, Troy Lee wrote:
> >>
> >>Hi Vinothkumar,
> >>
> >>Please refer to the following two changes in Gerrit:
> >>
> >>  * https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/39343
> >>    <https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/39343>
> >>  * https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344
> >>    <https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344>
> >>
> >Are these changes merged? I can't access these links.
> 
> Hi - We changed our process a bit and now patches are to be submitted to 
> openbmc/openbmc instead of openbmc/meta-aspeed.
> 
> To help with that transition I thought it would make sense to mark these 
> as hidden in Gerrit, but that seems to have gotten in the way a couple 
> times now.
> 
> I've changed the project flag again on all these meta-repos to read only 
> - you should be able to view them again now.
> 
> If we want any of these merged - they'll need to be re-submitted to 
> openbmc/openbmc.

That explains why I can't find these patches a week ago, and it appears
again yesterday. Thanks for pointing it out, I'll re-submit the change
against to openbmc/openbmc.

Thanks,
Troy Lee


  reply	other threads:[~2021-03-11  3:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 12:27 evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!' VINOTHKUMAR RK
2021-02-05  2:27 ` Troy Lee
2021-02-05  4:19   ` VINOTHKUMAR RK
2021-02-05  7:29     ` Troy Lee
2021-02-05  8:15       ` VINOTHKUMAR RK
2021-02-05  9:28         ` Troy Lee
2021-02-15 11:45           ` VINOTHKUMAR RK
2021-02-17  2:40             ` Troy Lee
2021-03-08  5:52   ` Thang Nguyen
2021-03-09 22:10     ` Brad Bishop
2021-03-11  3:11       ` Troy Lee [this message]
2021-03-11 12:00         ` Brad Bishop

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=20210311031107.GA2095174@aspeedtech.com \
    --to=troy_lee@aspeedtech.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=thang@os.amperecomputing.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.