From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: dinguyen@kernel.org, Meng.Li@windriver.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] arm64: dts: agilex/stratix10: fix pmu interrupt numbers" failed to apply to 4.19-stable tree
Date: Sun, 19 Jan 2020 14:04:09 -0500 [thread overview]
Message-ID: <20200119190409.GY1706@sasha-vm> (raw)
In-Reply-To: <1579359826132170@kroah.com>
On Sat, Jan 18, 2020 at 04:03:46PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-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 210de0e996aee8e360ccc9e173fe7f0a7ed2f695 Mon Sep 17 00:00:00 2001
>From: Dinh Nguyen <dinguyen@kernel.org>
>Date: Wed, 20 Nov 2019 09:15:17 -0600
>Subject: [PATCH] arm64: dts: agilex/stratix10: fix pmu interrupt numbers
>
>Fix up the correct interrupt numbers for the PMU unit on Agilex
>and Stratix10.
>
>Fixes: 78cd6a9d8e15 ("arm64: dts: Add base stratix 10 dtsi")
>Cc: linux-stable <stable@vger.kernel.org>
>Reported-by: Meng Li <Meng.Li@windriver.com>
>Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
I've dropped the agilex part because 4b36daf9ada3 ("arm64: dts: agilex:
Add initial support for Intel's Agilex SoCFPGA") doesn't exist in
kernels older than 5.4. Queued for all trees.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-01-19 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 15:03 FAILED: patch "[PATCH] arm64: dts: agilex/stratix10: fix pmu interrupt numbers" failed to apply to 4.19-stable tree gregkh
2020-01-19 19:04 ` Sasha Levin [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=20200119190409.GY1706@sasha-vm \
--to=sashal@kernel.org \
--cc=Meng.Li@windriver.com \
--cc=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox