All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexander.levin@verizon.com (Levin, Alexander)
To: linux-snps-arc@lists.infradead.org
Subject: ARC stable backport request
Date: Mon, 22 Aug 2016 14:14:55 -0400	[thread overview]
Message-ID: <20160822180616.GA17185@sasha-lappy> (raw)
In-Reply-To: <2ac8d0fc-9c67-e7c7-41f0-68cb34514019@synopsys.com>

On Mon, Aug 22, 2016@10:36:20AM -0700, Vineet Gupta wrote:
> Hi Stable Team,
> 
> Could you please backport upstream 20d780374c81c ("ARC: build: Better way to
> detect ISA compatible toolchain")
> 
> This is needed to let kernel building with newer gcc 6.x based tools.
> 
> Thx,
> -Vineet

What's the version range? It looks to me like it depends on 1f6ccfff6
("ARCv2: Support for ARCv2 ISA and HS38x cores") which means 4.2+?

-- 

Thanks,
Sasha

WARNING: multiple messages have this Message-ID (diff)
From: "Levin, Alexander" <alexander.levin@verizon.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	arcml <linux-snps-arc@lists.infradead.org>,
	Anton Kolesov <Anton.Kolesov@synopsys.com>
Subject: Re: ARC stable backport request
Date: Mon, 22 Aug 2016 14:14:55 -0400	[thread overview]
Message-ID: <20160822180616.GA17185@sasha-lappy> (raw)
In-Reply-To: <2ac8d0fc-9c67-e7c7-41f0-68cb34514019@synopsys.com>

On Mon, Aug 22, 2016 at 10:36:20AM -0700, Vineet Gupta wrote:
> Hi Stable Team,
> 
> Could you please backport upstream 20d780374c81c ("ARC: build: Better way to
> detect ISA compatible toolchain")
> 
> This is needed to let kernel building with newer gcc 6.x based tools.
> 
> Thx,
> -Vineet

What's the version range? It looks to me like it depends on 1f6ccfff6
("ARCv2: Support for ARCv2 ISA and HS38x cores") which means 4.2+?

-- 

Thanks,
Sasha

  reply	other threads:[~2016-08-22 18:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 17:36 ARC stable backport request Vineet Gupta
2016-08-22 17:36 ` Vineet Gupta
2016-08-22 18:14 ` Levin, Alexander [this message]
2016-08-22 18:14   ` Levin, Alexander
2016-08-22 18:37   ` Vineet Gupta
2016-08-22 18:37     ` Vineet Gupta
2016-09-05 13:02 ` Greg KH
2016-09-05 13:02   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2016-05-25 11:43 Vineet Gupta
2016-05-25 11:43 ` Vineet Gupta
2016-05-30 14:38 ` Jiri Slaby
2016-05-30 14:38   ` Jiri Slaby
2016-08-02  7:00 ` Greg KH
2016-08-02  7:00   ` Greg KH
2016-08-02  7:45   ` Jiri Slaby
2016-08-02  7:45     ` Jiri Slaby
2016-08-02 17:23     ` Vineet Gupta
2016-08-02 17:23       ` Vineet Gupta
2016-08-03  5:42     ` Greg KH
2016-08-03  5:42       ` Greg KH
2016-08-14 15:39 ` Greg KH
2016-08-14 15:39   ` Greg KH
2016-08-15  6:42   ` Alexey Brodkin
2016-08-15  6:42     ` Alexey Brodkin
2016-08-15  7:45     ` greg
2016-08-15  7:45       ` greg
2015-12-01  8:30 Vineet Gupta
2015-12-01  8:30 ` Vineet Gupta
2016-01-25 11:35 ` Jiri Slaby
2016-01-25 11:35   ` Jiri Slaby

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=20160822180616.GA17185@sasha-lappy \
    --to=alexander.levin@verizon.com \
    --cc=linux-snps-arc@lists.infradead.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.