Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	David Miller <davem@davemloft.net>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	oferh@marvell.com, igall@marvell.com, nadavh@marvell.com,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: inside-secure - do not parse the dma mask from dt
Date: Fri, 23 Jun 2017 16:35:42 +0200	[thread overview]
Message-ID: <20170623143542.GA26089@kwain> (raw)
In-Reply-To: <CAK8P3a2U58VE6nn1fA79W+Vx7Y2fTn5-fLS6h4TQ5Qw_8ZcRtg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

Hi Arnd,

On Fri, Jun 23, 2017 at 04:29:58PM +0200, Arnd Bergmann wrote:
> On Fri, Jun 23, 2017 at 4:05 PM, Antoine Tenart
> <antoine.tenart@free-electrons.com> wrote:
> >
> > As pointed our by Arnd (ic Cc) parsing the dma mask from the dt node of
> > the engine is broken. This property will be removed from the device
> > trees having an inside-secure safexcel engine node. While the
> > inside-secure won't fail because of this (as it will fallback to a
> > 64 bits mask), the code handling the dma-mask property is dead. This
> > patch removes it.
> 
> Do we also need a patch to update the DT binding?

You're right, we need to update the bindings documentation. I'll send a
patch for this as well.

Thanks!
Antoine

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-06-23 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 14:05 [PATCH] crypto: inside-secure - do not parse the dma mask from dt Antoine Tenart
2017-06-23 14:29 ` Arnd Bergmann
2017-06-23 14:35   ` Antoine Tenart [this message]
2017-07-18 10:35 ` Herbert Xu

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=20170623143542.GA26089@kwain \
    --to=antoine.tenart@free-electrons.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=gregory.clement@free-electrons.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=igall@marvell.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=nadavh@marvell.com \
    --cc=oferh@marvell.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox