linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Paul Walmsley <paul.walmsley@sifive.com>
To: linux-riscv@lists.infradead.org
Cc: yamada.masahiro@socionext.com, linux-kernel@vger.kernel.org
Subject: kbuild change breaks HiFive-U boot here
Date: Fri, 4 Oct 2019 10:48:12 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910041037590.15827@viisi.sifive.com> (raw)


Commit 858805b336be1cabb3d9033adaa3676574d12e37 ("kbuild: add $(BASH) to 
run scripts with bash-extension") breaks my kernel test flow that targets 
the HiFive Unleashed board.  The boot traps during BBL early boot and 
stops.  QEMU is unaffected.  Reverting 858805b336be fixes the issue.

I haven't yet had the opportunity to root-cause the issue.  The issue may 
be related to idiosyncracies in my local boot testing process, rather 
than this commit.


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2019-10-04 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 17:48 Paul Walmsley [this message]
2019-10-05  3:12 ` kbuild change breaks HiFive-U boot here Masahiro Yamada

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=alpine.DEB.2.21.9999.1910041037590.15827@viisi.sifive.com \
    --to=paul.walmsley@sifive.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).