From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2 0/3] u-boot recipe updates
Date: Wed, 4 Jul 2012 11:00:05 -0400 [thread overview]
Message-ID: <20120704150005.GD1817@windriver.com> (raw)
In-Reply-To: <20120704141259.GA1817@windriver.com>
[Re: [PATCHv2 0/3] u-boot recipe updates] On 04/07/2012 (Wed 10:12) Paul Gortmaker wrote:
> [Re: [PATCHv2 0/3] u-boot recipe updates] On 03/07/2012 (Tue 10:48) Saul Wold wrote:
>
> > On 07/01/2012 10:44 PM, Paul Gortmaker wrote:
> > >These are the oe-core updates required so that yocto can do
> > >a successful build of a working u-boot image for the mpc8315
> > >reference BSP.
> > >
> > >In v2, I've fixed up the issue where TARGET_PREFIX accidentally became
> > >specific to the one single recipe. That made the 3/3 patch in v1 no
> > >longer required. However, when build testing, I noticed that we
> > >were needlessly clobbering PARALLEL_MAKE for u-boot, which is not
> > >at all required, and just slows down builds. So a new patch is
> > >added to fix that, and we still have three total.
> > >
> > >I've built for the beagleboard with -j8 (twice), and the same for
> > >the 8315 BSP. I've also always built u-boot with -j10 or greater
> > >for countless powerpc images I've made in the last 1/2 dozen years.
> > >Looking at the git history, it appears this just came in with some
> > >large import, versus being an actively chosen individual setting.
> > >
> > >The 8315 specific patch that was sent to the yocto list earlier to
> > >enable building it (u-boot.bin) by default is unchanged, but I can
> > >resend that if it helps somehow.
> > >
> > >Paul.
> > >---
> > >
> > >Paul Gortmaker (3):
> > > u-boot: Don't make the -Os removal part of global settings.
> > > u-boot: make FILESDIR a shared setting.
> > > u-boot: do not clobber PARALLEL_MAKE setting
> > >
> > Took in patches 1 & 3 into OE-Core
>
> Thanks!
>
> >
> > Looking for an update for FILESDIR -> FILESPATH as suggested by Richard.
>
> I've not seen Richard's feedback, since I'm OOO, and with the To/Cc:
> stripped, it has got archived vs. staying in my inbox. [They get
> archived, because just like LKML, I'm not going to pretend I can read
> all poky/oe mail on the very day it arrives.]
I've found Richard's comments [looking in OE archive and not poky
helped] and will test what he proposed to replace FILESDIR. But I still
think it extremely worthwhile if some fine tuning to the mailing list(s)
can be done to address what I mentioned below.
Thanks,
Paul.
--
>
> On a related note, is it possible to fix the mailing list so that it
> does not strip To/Cc information and Message-ID strings? [I'd have to
> check -- maybe it is (also) inserting a needless Reply-To: header that
> messes things up.]
>
> Further, without a proper Message-ID, it breaks patchworks, so Richard's
> comments should be here:
>
> http://patchwork.openembedded.org/patch/30879/
>
> but unfortunately they are not. The netdev and ppc dev lists for linux
> use patchworks and have the follow-up review comments captured and it is
> really quite useful to all (esp. the person who has to triage and
> decruftify patchworks content/state once a month...)
>
> Finally, I can't even find it in the June/July archives:
>
> https://lists.yoctoproject.org/pipermail/poky/2012-July/subject.html
>
> Just thought it worth a mention, in case it hasn't been mentioned
> before. Fixing these little quirks would lower the barrier to entry
> and the frustration factor for new contributors. If I can help out
> somehow with testing a fix, let me know.
>
> Thanks,
> Paul.
> --
>
> >
> > Thanks
> > Sau!
> >
> >
> > > meta/recipes-bsp/u-boot/u-boot.inc | 6 ++----
> > > meta/recipes-bsp/u-boot/u-boot_2011.03.bb | 2 --
> > > meta/recipes-bsp/u-boot/u-boot_2011.06.bb | 2 --
> > > meta/recipes-bsp/u-boot/u-boot_2012.04.01.bb | 2 --
> > > 4 files changed, 2 insertions(+), 10 deletions(-)
> > >
next prev parent reply other threads:[~2012-07-04 15:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 18:35 [PATCH 0/3] u-boot recipe updates Paul Gortmaker
2012-06-29 18:35 ` [PATCH 1/3] u-boot: Don't make the -Os removal part of global settings Paul Gortmaker
2012-06-29 21:55 ` Khem Raj
2012-06-29 22:01 ` Wolfgang Denk
2012-06-29 22:11 ` Khem Raj
2012-06-29 23:34 ` Wolfgang Denk
2012-06-30 2:49 ` Khem Raj
2012-07-01 22:03 ` Saul Wold
2012-07-01 23:14 ` Khem Raj
2012-07-02 3:04 ` Paul Gortmaker
2012-07-02 5:44 ` [PATCHv2 0/3] u-boot recipe updates Paul Gortmaker
2012-07-02 5:44 ` [PATCHv2 1/3] u-boot: Don't make the -Os removal part of global settings Paul Gortmaker
2012-07-02 11:23 ` Otavio Salvador
2012-07-02 5:44 ` [PATCHv2 2/3] u-boot: make FILESDIR a shared setting Paul Gortmaker
2012-07-02 11:24 ` Otavio Salvador
2012-07-02 13:33 ` Chris Larson
2012-07-02 16:42 ` Otavio Salvador
2012-07-02 19:03 ` Richard Purdie
2012-07-02 5:44 ` [PATCHv2 3/3] u-boot: do not clobber PARALLEL_MAKE setting Paul Gortmaker
2012-07-02 11:25 ` Otavio Salvador
2012-07-03 17:48 ` [PATCHv2 0/3] u-boot recipe updates Saul Wold
2012-07-04 14:12 ` Paul Gortmaker
2012-07-04 15:00 ` Paul Gortmaker [this message]
2012-07-04 15:29 ` Phil Blundell
2012-07-05 16:14 ` Paul Gortmaker
2012-07-09 16:01 ` Phil Blundell
2012-07-09 18:20 ` McClintock Matthew-B29882
2012-07-09 18:52 ` Paul Gortmaker
2012-07-09 19:08 ` Richard Purdie
2012-07-04 15:23 ` [PATCH] u-boot: make FILESDIR a shared setting via FILESPATH Paul Gortmaker
2012-07-04 15:38 ` Martin Jansa
2012-07-04 17:01 ` Richard Purdie
2012-07-05 17:19 ` Saul Wold
2012-06-29 18:35 ` [PATCH 2/3] u-boot: make FILESDIR a shared setting Paul Gortmaker
2012-06-29 18:35 ` [PATCH 3/3] u-boot: make sure CROSS_COMPILE is passed into build Paul Gortmaker
2012-06-29 20:04 ` McClintock Matthew-B29882
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=20120704150005.GD1817@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox