linux-kernel - Re: stable 3.14 backport request for ARC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <C2D7FE5348E1B147BCA15975FBA2307565BCD86E@IN01WEMBXA.internal.synopsys.com>
Date:	Wed, 21 Jan 2015 06:33:52 +0000
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	Greg KH <greg@...ah.com>
CC:	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: stable 3.14 backport request for ARC

On Monday 19 January 2015 07:03 PM, Greg KH wrote:

On Tue, Dec 23, 2014 at 08:08:51AM +0000, Vineet Gupta wrote:

> 2014-04-18 64ee9f32c33c ARC: Delete stale barrier.h

I don't see how this is an issue for 3.14, it says it fixes a 3.15 build
issue only, so I didn't apply it.  Why did you ask for it?

Technically it was indeed detected in 3.15 but the offending commit was merged in 3.14 (93ea02bb8435 arch: Clean up asm/barrier.h implementations using asm-generic/barrier.h)
I'm ok if you think it doesn't qualify !

FWIW, as an addendum to my prev email I'd also requested for the following backport.
Perhaps you will do that when u eventually get to that email from ur backlog. Otherwise, the details are below.

2014-06-24 ba25915fb2cd ARC: Fix build breakage for !CONFIG_ARC_DW2_UNWIND

Thx,
-Vineet
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/