From: Jason Cooper <jason@lakedaemon.net>
To: Rob Landley <rob@landley.net>
Cc: Rich Felker <dalias@libc.org>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Fix building j2_defconfig
Date: Tue, 16 Aug 2016 21:23:49 +0000 [thread overview]
Message-ID: <20160816212349.GS3353@io.lakedaemon.net> (raw)
In-Reply-To: <398e6385-ec40-4493-449d-c8c43fd11d85@landley.net>
Hi Rob,
On Tue, Aug 16, 2016 at 04:15:22PM -0500, Rob Landley wrote:
> On 08/16/2016 10:41 AM, Jason Cooper wrote:
> > When targeting the j2, we need to retain '-m2'. Previously, the
> > Makefile blew out -m2 on the next line via :=.
> >
> > Fix this by s/:=/+=/ when building for the J2.
> >
> > Fixes: 5a846abad07f6 ("sh: add support for J-Core J2 processor")
> > Signed-off-by: Jason Cooper <jason@lakedaemon.net>
>
> Speaking of j2, any status on the missing pieces of infratsructure that
> went in through other trees, without which booting hangs awaiting the
> first interrupt?
>
> http://lists.j-core.org/pipermail/j-core/2016-August/000326.html
>
> It would be nice if the rest of the board support could make it in this
> release. Which trees are they going through?
I'm not aware of the status of other bits, but the irqchip driver can be
found [1] in a stable, based off of v4.8-rc1, branch here:
git://git.infradead.org/users/jcooper/linux.git irqchip/jcore
hth,
Jason.
[1] Now that I got the damn toolchain fixed and j2_defconfig building...
next prev parent reply other threads:[~2016-08-16 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 15:41 [PATCH] sh: Fix building j2_defconfig Jason Cooper
2016-08-16 21:15 ` Rob Landley
2016-08-16 21:23 ` Jason Cooper [this message]
2016-08-20 3:40 ` Rob Landley
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=20160816212349.GS3353@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
/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