From: Cristian Stoica <cristian.stoica@freescale.com>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: <horia.geanta@freescale.com>, <linux-crypto@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] crypto: caam: fix some compile warnings
Date: Thu, 5 Mar 2015 09:12:13 +0200 [thread overview]
Message-ID: <54F801CD.7040706@freescale.com> (raw)
In-Reply-To: <20150304123419.7baecac7320d5b3483449dab@freescale.com>
On 03/04/2015 08:34 PM, Kim Phillips wrote:
> I don't see how, e.g., for one, dma_map_sg is I/O TLB
> implementation-dependent.
I'll need some remedial classes on this topic, but for the moment I
don't see how this matters for mapping sg chains. Can you share some
pointers?
Thanks,
Cristian S.
next prev parent reply other threads:[~2015-03-05 7:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 6:50 [PATCH 0/3] fix some CAAM warnings yanjiang.jin
2015-03-03 6:50 ` [PATCH 1/3] crypto: caam: fix some compile warnings yanjiang.jin
2015-03-03 18:59 ` Kim Phillips
2015-03-04 2:32 ` yjin
2015-03-04 4:57 ` yjin
2015-03-04 9:03 ` Cristian Stoica
2015-03-04 18:34 ` Kim Phillips
2015-03-05 7:12 ` Cristian Stoica [this message]
2015-03-06 0:38 ` Kim Phillips
2015-03-04 8:48 ` Cristian Stoica
2015-03-04 9:11 ` Cristian Stoica
2015-03-03 6:50 ` [PATCH 2/3] crypto: caam_rng: fix rng_unmap_ctx's DMA_UNMAP size problem yanjiang.jin
2015-03-03 19:31 ` Kim Phillips
2015-03-04 5:33 ` yjin
2015-03-04 18:36 ` Kim Phillips
2015-03-05 2:52 ` yjin
2015-03-06 0:28 ` Kim Phillips
2015-03-03 6:50 ` [PATCH 3/3] crypto: caamhash: - fix uninitialized edesc->sec4_sg_bytes field yanjiang.jin
2015-03-03 13:39 ` [PATCH 0/3] fix some CAAM warnings Horia Geantă
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=54F801CD.7040706@freescale.com \
--to=cristian.stoica@freescale.com \
--cc=horia.geanta@freescale.com \
--cc=kim.phillips@freescale.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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).