All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vgupta@synopsys.com>
To: gregkh@linuxfoundation.org, noamc@ezchip.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ARC: Make ARC bitops "safer" (add anti-optimization)" failed to apply to 4.1-stable tree
Date: Sat, 08 Aug 2015 13:17:37 +0530	[thread overview]
Message-ID: <55C5B419.2010000@synopsys.com> (raw)
In-Reply-To: <143898009716527@kroah.com>

On Saturday 08 August 2015 02:11 AM, gregkh@linuxfoundation.org wrote:
> The patch below does not apply to the 4.1-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
> 
> thanks,
> 
> greg k-h
> 
> ------------------ original commit in Linus's tree ------------------
> 
> From 80f420842ff42ad61f84584716d74ef635f13892 Mon Sep 17 00:00:00 2001
> From: Vineet Gupta <vgupta@synopsys.com>
> Date: Fri, 3 Jul 2015 11:26:22 +0530
> Subject: [PATCH] ARC: Make ARC bitops "safer" (add anti-optimization)
> 
....
> 
> Fixes STAR 9000866918 ("unsafe "undefined behavior" code in kernel")
> 
> Reported-by: Noam Camus <noamc@ezchip.com>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>


Hi Greg,

This needs a pre-requisite patch backport. Could you please apply below to 4.1

04e2eee4b02e ARC: Reduce bitops lines of code using macros

Thx,
-Vineet

      reply	other threads:[~2015-08-08  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 20:41 FAILED: patch "[PATCH] ARC: Make ARC bitops "safer" (add anti-optimization)" failed to apply to 4.1-stable tree gregkh
2015-08-08  7:47 ` Vineet Gupta [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=55C5B419.2010000@synopsys.com \
    --to=vgupta@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=noamc@ezchip.com \
    --cc=stable@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.