From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: monakov.y@gmail.com, andrew.murray@arm.com,
lorenzo.pieralisi@arm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] PCI: keystone: Fix link training retries initiation" failed to apply to 4.19-stable tree
Date: Thu, 6 Feb 2020 18:24:37 -0500 [thread overview]
Message-ID: <20200206232437.GP31482@sasha-vm> (raw)
In-Reply-To: <158101600590150@kroah.com>
On Thu, Feb 06, 2020 at 08:06:45PM +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 6df19872d881641e6394f93ef2938cffcbdae5bb Mon Sep 17 00:00:00 2001
>From: Yurii Monakov <monakov.y@gmail.com>
>Date: Tue, 17 Dec 2019 14:38:36 +0300
>Subject: [PATCH] PCI: keystone: Fix link training retries initiation
>
>ks_pcie_stop_link() function does not clear LTSSM_EN_VAL bit so
>link training was not triggered more than once after startup.
>In configurations where link can be unstable during early boot,
>for example, under low temperature, it will never be established.
>
>Fixes: 0c4ffcfe1fbc ("PCI: keystone: Add TI Keystone PCIe driver")
>Signed-off-by: Yurii Monakov <monakov.y@gmail.com>
>Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>Acked-by: Andrew Murray <andrew.murray@arm.com>
>Cc: stable@vger.kernel.org
The code got moved around by b492aca35c98 ("PCI: keystone: Merge
pci-keystone-dw.c and pci-keystone.c"). I've fixed it up and queued for
all branches.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-06 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 19:06 FAILED: patch "[PATCH] PCI: keystone: Fix link training retries initiation" failed to apply to 4.19-stable tree gregkh
2020-02-06 23:24 ` 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=20200206232437.GP31482@sasha-vm \
--to=sashal@kernel.org \
--cc=andrew.murray@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=monakov.y@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox