All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Jon Mason <jdmason@kudzu.us>
Cc: Jon Mason <jon.mason@arm.com>,
	meta-arm@lists.yoctoproject.org, nd@arm.com,
	 Damodar Santhapuri <damodar.santhapuri@arm.com>
Subject: Re: [meta-arm] [PATCH] arm-bsp: u-boot error fixing and file clean-up
Date: Tue, 21 Jul 2020 15:12:47 +0100	[thread overview]
Message-ID: <3c3634f24ee87b5ea036372e0cdec93fef26456a.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200721134830.GA30432@kudzu.us>

On Tue, 2020-07-21 at 09:48 -0400, Jon Mason wrote:
> On Tue, Jul 21, 2020 at 09:55:47AM +0100, Richard Purdie wrote:
> > On Mon, 2020-07-20 at 14:17 -0400, Jon Mason wrote:
> > > This commit fixes the errors while rebasing u-boot src to
> > > v2020.07.
> > > Additional work necessary to preserve dunfell functionality.
> > > Consolidate all of the files into a single inc file and single
> > > bbappend
> > > file.
> > > 
> > > Change-Id: I442c843b1fafeb41ea283d2f11393522a48fc9d2
> > > Signed-off-by: Damodar Santhapuri <damodar.santhapuri@arm.com>
> > > Signed-off-by: Jon Mason <jon.mason@arm.com>
> > 
> > Thanks, looking forward to green builds!
> 
> I'm not sure this gets us to green, but it gets us out of the red for
> sure ;-).
> 
> It's in master now.  Now Ross can start fixing all the warnings.

Ross' plan here seems to be to file them as bitbake bugs and force the
bitbake maintainer to write patches! ;-)

The last test build didn't throw any warnings so we may be looking ok
there too...

Cheers,

Richard


      reply	other threads:[~2020-07-21 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 18:17 [PATCH] arm-bsp: u-boot error fixing and file clean-up Jon Mason
2020-07-21  8:55 ` [meta-arm] " Richard Purdie
2020-07-21 13:48   ` Jon Mason
2020-07-21 14:12     ` Richard Purdie [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=3c3634f24ee87b5ea036372e0cdec93fef26456a.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=damodar.santhapuri@arm.com \
    --cc=jdmason@kudzu.us \
    --cc=jon.mason@arm.com \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=nd@arm.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.