linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: marvell: mark the cp110 crypto engine as dma coherent
Date: Tue, 18 Jul 2017 12:03:19 +0200	[thread overview]
Message-ID: <87bmoi83ko.fsf@free-electrons.com> (raw)
In-Reply-To: <20170718095130.GC2563@kwain> (Antoine Tenart's message of "Tue, 18 Jul 2017 11:51:30 +0200")

Hi Antoine,
 
 On mar., juil. 18 2017, Antoine Tenart <antoine.tenart@free-electrons.com> wrote:

> Hi Gregory,
>
> On Tue, Jul 18, 2017 at 11:45:24AM +0200, Gregory CLEMENT wrote:
>>  On lun., juil. 17 2017, Antoine Tenart <antoine.tenart@free-electrons.com> wrote:
>> 
>> > The crypto engines found on the cp110 master and slave are dma coherent.
>> > This patch adds the relevant property to their dt nodes.
>> 
>> Is it a fix?
>> 
>> Should it go to the current ans stable kernel?
>
> Yes I think that should go into stable. I forgot the stable tag, do you
> want me to send a v2 with it included?
>
Yes please and also add the Fixes tag.

Thanks,

Gregory

> Thanks!
> Antoine

>
> -- 
> Antoine T?nart, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2017-07-18 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17  7:35 [PATCH] arm64: dts: marvell: mark the cp110 crypto engine as dma coherent Antoine Tenart
2017-07-18  9:45 ` Gregory CLEMENT
2017-07-18  9:51   ` Antoine Tenart
2017-07-18 10:03     ` Gregory CLEMENT [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=87bmoi83ko.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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).