Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] ne10: use bb.debug for debug messages
Date: Thu, 21 Apr 2016 21:04:10 -0400	[thread overview]
Message-ID: <20160422010410.GS16135@denix.org> (raw)
In-Reply-To: <CA+chaQfEgVEExME523XvcqQBc53U3WVuFO48s6ArMkpmt8kW8g@mail.gmail.com>

On Wed, Apr 20, 2016 at 10:44:04PM +0200, Martin Jansa wrote:
> When everything is at least once tested in my jenkins builds and I've time
> to go through the list of pending changes.
> 
> I was away from computers almost whole previous week, so there is longer
> delay now.

Thanks, no problem and congrats!


> On Wed, Apr 20, 2016 at 8:25 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> 
> > Ping. Also in master-next for over a week - how often does it get merged to
> > master?
> >
> >
> > On Thu, Apr 07, 2016 at 04:40:00PM -0400, Denys Dmytriyenko wrote:
> > > From: Denys Dmytriyenko <denys@ti.com>
> > >
> > > Moreover, the messages are misleading, saying "Building for arch blah",
> > > even when this recipe is not being built. It merely checks if the recipe
> > > is cmaptible with the currently used architecture.
> > >
> > > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > > ---
> > >  meta-oe/recipes-support/ne10/ne10_1.2.1.bb | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/meta-oe/recipes-support/ne10/ne10_1.2.1.bb
> > b/meta-oe/recipes-support/ne10/ne10_1.2.1.bb
> > > index 4d753a0..de97982 100644
> > > --- a/meta-oe/recipes-support/ne10/ne10_1.2.1.bb
> > > +++ b/meta-oe/recipes-support/ne10/ne10_1.2.1.bb
> > > @@ -20,10 +20,10 @@ COMPATIBLE_MACHINE_armv7a = "(.*)"
> > >  python () {
> > >      if any(t.startswith('armv7') for t in d.getVar('TUNE_FEATURES',
> > True).split()):
> > >          d.setVar('NE10_TARGET_ARCH', 'armv7')
> > > -        bb.note('Building Ne10 for armv7')
> > > +        bb.debug(2, 'Building Ne10 for armv7')
> > >      elif any(t.startswith('aarch64') for t in d.getVar('TUNE_FEATURES',
> > True).split()):
> > >          d.setVar('NE10_TARGET_ARCH', 'aarch64')
> > > -        bb.note('Building Ne10 for aarch64')
> > > +        bb.debug(2, 'Building Ne10 for aarch64')
> > >      else:
> > >          raise bb.parse.SkipPackage("Incompatible with archs other than
> > armv7 and aarch64")
> > >  }
> > > --
> > > 2.2.0
> > >
> > > --
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > Openembedded-devel@lists.openembedded.org
> > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel


      reply	other threads:[~2016-04-22  1:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 20:40 [PATCH] ne10: use bb.debug for debug messages Denys Dmytriyenko
2016-04-07 22:47 ` Khem Raj
2016-04-20 18:25 ` Denys Dmytriyenko
2016-04-20 20:44   ` Martin Jansa
2016-04-22  1:04     ` Denys Dmytriyenko [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=20160422010410.GS16135@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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