From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: qiangqing.zhang@nxp.com, mkl@pengutronix.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] can: flexcan: disable completely the ECC mechanism" failed to apply to 4.14-stable tree
Date: Mon, 11 Nov 2019 09:44:01 -0500 [thread overview]
Message-ID: <20191111144401.GF8496@sasha-vm> (raw)
In-Reply-To: <157345390614177@kroah.com>
On Mon, Nov 11, 2019 at 07:31:46AM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.14-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 5e269324db5adb2f5f6ec9a93a9c7b0672932b47 Mon Sep 17 00:00:00 2001
>From: Joakim Zhang <qiangqing.zhang@nxp.com>
>Date: Thu, 15 Aug 2019 08:00:26 +0000
>Subject: [PATCH] can: flexcan: disable completely the ECC mechanism
>
>The ECC (memory error detection and correction) mechanism can be
>activated or not, controlled by the ECCDIS bit in CAN_MECR. When
>disabled, updates on indications and reporting registers are stopped.
>So if want to disable ECC completely, had better assert ECCDIS bit, not
>just mask the related interrupts.
>
>Fixes: cdce844865be ("can: flexcan: add vf610 support for FlexCAN")
>Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
>Cc: linux-stable <stable@vger.kernel.org>
>Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
I've adjusted the patch to work around missing 88462d2a7830 ("can:
flexcan: Remodel FlexCAN register r/w APIs for big endian FlexCAN
controllers.") and queued it for 4.14-4.4.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-11-11 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 6:31 FAILED: patch "[PATCH] can: flexcan: disable completely the ECC mechanism" failed to apply to 4.14-stable tree gregkh
2019-11-11 14:44 ` Sasha Levin [this message]
2019-11-11 14:58 ` Greg KH
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=20191111144401.GF8496@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=mkl@pengutronix.de \
--cc=qiangqing.zhang@nxp.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;
as well as URLs for NNTP newsgroup(s).