All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <private@roeck-us.net>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Cc: "arc-linux-dev@synopsys.com" <arc-linux-dev@synopsys.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Subject: Re: ARCv2 testing exposure (Re: arc build failures in -next due to ARCv2 patch)
Date: Mon, 31 Aug 2015 06:58:44 -0700	[thread overview]
Message-ID: <55E45D94.4050604@roeck-us.net> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA23075CFB8734F@IN01WEMBXB.internal.synopsys.com>

Hi Vineet,

On 08/31/2015 03:35 AM, Vineet Gupta wrote:
> I was wondering about ARCv2 coverage in your build service. Do you have the needed 2nd toolchain for ARCv2 as well. If not can u add it please. To build one, you could use upstream buildroot or the legacy scripts at git@github.com:foss-for-synopsys-dwc-arc-processors/toolchain.git Or if you so prefer, we also have prebuilt toolchains in github releases. Thx, -Vineet 

Thanks for the information.

I created a toolchain using buildroot, and the build service already covers arcv2.

Guenter

      reply	other threads:[~2015-08-31 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 23:58 arc build failures in -next due to ARCv2 patch Guenter Roeck
2015-06-27 11:42 ` Vineet Gupta
2015-06-27 14:16   ` Guenter Roeck
2015-06-28 15:16     ` Vineet Gupta
2015-08-31 10:35       ` ARCv2 testing exposure (Re: arc build failures in -next due to ARCv2 patch) Vineet Gupta
2015-08-31 13:58         ` Guenter Roeck [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=55E45D94.4050604@roeck-us.net \
    --to=private@roeck-us.net \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=arc-linux-dev@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.