All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org, James Hogan <james.hogan@imgtec.com>
Subject: Re: FAILED: patch "[PATCH] MIPS: IP22: Fix build error due to binutils 2.25 uselessnes." failed to apply to 4.10-stable tree
Date: Wed, 8 Mar 2017 10:16:45 +0100	[thread overview]
Message-ID: <20170308091645.GA17774@linux-mips.org> (raw)
In-Reply-To: <14889560764620@kroah.com>

Hi Gregh,

On Wed, Mar 08, 2017 at 07:54:36AM +0100, gregkh@linuxfoundation.org wrote:

> The patch below does not apply to the 4.10-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 ae2f5e5ed04a17c1aa1f0a3714c725e12c21d2a9 Mon Sep 17 00:00:00 2001
> From: Ralf Baechle <ralf@linux-mips.org>
> Date: Thu, 15 Dec 2016 12:39:22 +0100
> Subject: [PATCH] MIPS: IP22: Fix build error due to binutils 2.25 uselessnes.

The patch will apply fine to v4.10-stable but requires 55e4fac7c9ef
("MIPS: IP22: Reformat inline assembler code to modern standards.")
to be applied first.  This is the case for all three branches that you
reported this issue with, v4.10-stable, v4.9-stable and v4.4-stable.

  Ralf

  reply	other threads:[~2017-03-08 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  6:54 FAILED: patch "[PATCH] MIPS: IP22: Fix build error due to binutils 2.25 uselessnes." failed to apply to 4.10-stable tree gregkh
2017-03-08  9:16 ` Ralf Baechle [this message]
2017-03-08  9:53   ` Greg KH
2017-03-08 10:00     ` Ralf Baechle

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=20170308091645.GA17774@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.hogan@imgtec.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.