From: Greg KH <greg@kroah.com>
To: Antoine Tenart <antoine.tenart@free-electrons.com>
Cc: stable@vger.kernel.org, gregory.clement@free-electrons.com,
thomas.petazzoni@free-electrons.com,
miquel.raynal@free-electrons.com
Subject: Re: [PATCH] arm64: dts: marvell: mark the cp110 crypto engine as dma coherent
Date: Mon, 13 Nov 2017 17:12:54 +0100 [thread overview]
Message-ID: <20171113161254.GA27516@kroah.com> (raw)
In-Reply-To: <20171113155122.12710-1-antoine.tenart@free-electrons.com>
On Mon, Nov 13, 2017 at 04:51:22PM +0100, Antoine Tenart wrote:
> commit ec0aef9881d18aa781268ec9cba8eba5b202f5b4 upstream.
>
> The crypto engines found on the cp110 master and slave are dma coherent.
> This patch adds the relevant property to their dt nodes.
>
> Cc: stable@vger.kernel.org # v4.12+
> Fixes: 973020fd9498 ("arm64: marvell: dts: add crypto engine description for 7k/8k")
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> ---
>
> Hi,
>
> This patch did not apply to the 4.12-stable tree. Since the original
> patch made it to Linus tree, this is a version which applies nicely
> to the 4.12-stable tree.
4.12 is long end-of-life, no one is maintaining it, so there's no tree
to apply it to, sorry.
The front page of kernel.org usually is a good summary of the trees that
are still "alive" if you need to figure it out.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-13 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 15:51 [PATCH] arm64: dts: marvell: mark the cp110 crypto engine as dma coherent Antoine Tenart
2017-11-13 15:55 ` Antoine Tenart
2017-11-13 16:12 ` Greg KH [this message]
2017-11-13 16:41 ` Antoine Tenart
-- strict thread matches above, loose matches on Subject: below --
2017-07-17 7:35 Antoine Tenart
2017-07-18 9:45 ` Gregory CLEMENT
2017-07-18 9:51 ` Antoine Tenart
2017-07-18 10:03 ` Gregory CLEMENT
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=20171113161254.GA27516@kroah.com \
--to=greg@kroah.com \
--cc=antoine.tenart@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=miquel.raynal@free-electrons.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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 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.