From: Christoph Hellwig <hch@lst.de>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Aymen Sghaier <aymen.sghaier@nxp.com>,
Christoph Hellwig <hch@lst.de>,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com
Subject: Re: [PATCH] crypto: caam - fix zero-length buffer DMA mapping
Date: Wed, 19 Dec 2018 15:41:05 +0100 [thread overview]
Message-ID: <20181219144105.GA23389@lst.de> (raw)
In-Reply-To: <20181219143644.22089-1-horia.geanta@nxp.com>
Yes, we should never do zero-length dma mappings, so this looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: Aymen Sghaier <aymen.sghaier@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com
Subject: Re: [PATCH] crypto: caam - fix zero-length buffer DMA mapping
Date: Wed, 19 Dec 2018 15:41:05 +0100 [thread overview]
Message-ID: <20181219144105.GA23389@lst.de> (raw)
In-Reply-To: <20181219143644.22089-1-horia.geanta@nxp.com>
Yes, we should never do zero-length dma mappings, so this looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-19 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 14:36 [PATCH] crypto: caam - fix zero-length buffer DMA mapping Horia Geantă
2018-12-19 14:36 ` Horia Geantă
2018-12-19 14:41 ` Christoph Hellwig [this message]
2018-12-19 14:41 ` Christoph Hellwig
2019-01-10 14:03 ` Herbert Xu
2019-01-10 14:03 ` 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=20181219144105.GA23389@lst.de \
--to=hch@lst.de \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.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.