stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: sashal@kernel.org, stable@vger.kernel.org
Subject: Re: patch for mips build failure in 5.4-stable
Date: Fri, 20 Nov 2020 09:34:20 +0100	[thread overview]
Message-ID: <X7d/jEoEm6yEUpPZ@kroah.com> (raw)
In-Reply-To: <20201119103911.rbqxmssqe2pqnli2@debian>

On Thu, Nov 19, 2020 at 10:39:11AM +0000, Sudip Mukherjee wrote:
> Hi Greg, Sasha,
> 
> While backporting 37640adbefd6 ("MIPS: PCI: remember nasid changed by
> set interrupt affinity") something went wrong and an extra 'n' was added.
> So 'data->nasid' became 'data->nnasid' and the MIPS builds started failing.
> 
> Since v5.4.78 is already released I assumed you will need a patch to
> fix it. Please consider applying the attached patch, this is only needed
> for 5.4-stable tree.

Now applied, thanks!

greg k-h

      reply	other threads:[~2020-11-20  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 10:39 patch for mips build failure in 5.4-stable Sudip Mukherjee
2020-11-20  8:34 ` Greg Kroah-Hartman [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=X7d/jEoEm6yEUpPZ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).