From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] data: Move warning code to the first loop for performance
Date: Tue, 26 May 2015 10:59:44 +0100 [thread overview]
Message-ID: <1432634384.404.0.camel@linuxfoundation.org> (raw)
In-Reply-To: <D4CFEBC3-6C2F-4142-9DB2-9BCACFA3DE07@gmail.com>
On Tue, 2015-05-26 at 11:56 +0200, Bernhard Reutner-Fischer wrote:
> On May 25, 2015 9:53:52 AM GMT+02:00, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> >By doing this we can take advantage of the expansion cache before
> >starting write operations on the data store.
> >
> >Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> >
> >diff --git a/bitbake/lib/bb/data.py b/bitbake/lib/bb/data.py
> >index 82eefef..218998a 100644
> >--- a/bitbake/lib/bb/data.py
> >+++ b/bitbake/lib/bb/data.py
> >@@ -156,17 +156,17 @@ def expandKeys(alterdata, readdata = None):
> > if key == ekey:
> > continue
> > todolist[key] = ekey
> >+ newval = alterdata.getVar(ekey, 0)
> >+ if newval:
> >+ val = alterdata.getVar(key, 0)
> >+ if val is not None and newval is not None:
>
> newval cannot ever be None in this if.
True, to be fair I just moved the code although I probably was
responsible for the original too.
I'll tweak it, thanks.
Cheers,
Richard
prev parent reply other threads:[~2015-05-26 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 7:53 [PATCH] data: Move warning code to the first loop for performance Richard Purdie
2015-05-26 9:56 ` Bernhard Reutner-Fischer
2015-05-26 9:59 ` 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=1432634384.404.0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=rep.dot.nop@gmail.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.