All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bystricky, Juro" <juro.bystricky@intel.com>
To: Marek Vasut <marex@denx.de>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "jurobystricky@hotmail.com" <jurobystricky@hotmail.com>,
	"Gan, Yau Wai" <yau.wai.gan@intel.com>
Subject: Re: [PATCH] siteinfo: nios2-linux - remove wrong mutex info
Date: Tue, 3 Oct 2017 20:44:26 +0000	[thread overview]
Message-ID: <6E51916E4A1F32428260031F4C7CD2B611A22BC6@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <0794973c-f52e-b63f-010e-2bf72b76cb5a@denx.de>


> While I understand ARM/ is wrong, why is removing the db_cv_mutex a
> correct fix instead of ie. s/ARM/nios2/ ? The patch description does not
> explain that.

With the relatively recent commit http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/recipes-support/db?id=f4e8e9242c5df095b52688b083df3c9d36e7144b
some nios2 builds (uboot, core-image-minimal, etc) were broken due to db trying to
use ARM instructions in mutexes. The reason was db "configure" used the cached entry 
from nios2-linux (which was incorrect).  So the remedy was to remove the incorrect cached entry
and let db "configure" figure out which is the proper mutex to use. 
Besides, I don't even know if nios2/gcc-assembly exists.
Also, none of other Linux info files provides this entry (db_cv_mutex).



  reply	other threads:[~2017-10-03 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 19:51 [PATCH] siteinfo: nios2-linux - remove wrong mutex info Juro Bystricky
2017-10-03 19:59 ` Marek Vasut
2017-10-03 20:44   ` Bystricky, Juro [this message]
2017-10-03 20:52     ` Marek Vasut

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=6E51916E4A1F32428260031F4C7CD2B611A22BC6@ORSMSX112.amr.corp.intel.com \
    --to=juro.bystricky@intel.com \
    --cc=jurobystricky@hotmail.com \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yau.wai.gan@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 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.