mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stafford Horne <shorne@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	openrisc@lists.librecores.org
Subject: Re: [OpenRISC] Build regressions/improvements in v4.11-rc2
Date: Tue, 14 Mar 2017 22:36:47 +1100	[thread overview]
Message-ID: <87shmgum28.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170313151001.GB2418@lianli.shorne-pla.net>

Stafford Horne <shorne@gmail.com> writes:
> On Mon, Mar 13, 2017 at 03:17:15PM +0100, Geert Uytterhoeven wrote:
>> >>
>> >> OpenRISC needs an updated toolchain.
>> >
>> > Thansk for the report.  I have updated the toolchain that is pointed to
>> > by make.cross [1] a few weeks back.  Fengguang and I updated the
>> > make.cross tool which the build robot's point to a late tool chain [2],
>> > what are you using?
>> 
>> I'm using the linux-next build service.
>> http://kisskb.ellerman.id.au/kisskb/head/4495c08e84729385774601b5146d51d9e5849f81/
>
> Right, I see the results there but I don't really see how to go about
> sending patches to reference our latest toolchain.
>
> Perhaps Michael can help with that.

I can. It's fixed now:

  http://kisskb.ellerman.id.au/kisskb/buildresult/12965819/

Thanks for the pointer to the toolchain.

cheers

  reply	other threads:[~2017-03-14 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13  8:43 Geert Uytterhoeven
2017-03-13 10:15 ` Geert Uytterhoeven
2017-03-13 14:12   ` [OpenRISC] " Stafford Horne
2017-03-13 14:17     ` Geert Uytterhoeven
2017-03-13 15:10       ` Stafford Horne
2017-03-14 11:36         ` Michael Ellerman [this message]
2017-03-14 12:54           ` Stafford Horne

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=87shmgum28.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shorne@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®