From: Cristian Stoica Subject: Re: [PATCH 1/3] crypto: caam: fix some compile warnings Date: Wed, 4 Mar 2015 11:03:28 +0200 Message-ID: <54F6CA60.5030905@freescale.com> References: <1425365453-19358-1-git-send-email-yanjiang.jin@windriver.com> <1425365453-19358-2-git-send-email-yanjiang.jin@windriver.com> <20150303125953.8585904680288a9734566b42@freescale.com> <54F66EA3.7080506@windriver.com> <54F6909D.8040002@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: , , , , , , , To: yjin , Kim Phillips Return-path: Received: from mail-bn1on0140.outbound.protection.outlook.com ([157.56.110.140]:20058 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758042AbbCDJDi (ORCPT ); Wed, 4 Mar 2015 04:03:38 -0500 In-Reply-To: <54F6909D.8040002@windriver.com> Sender: linux-crypto-owner@vger.kernel.org List-ID: On 03/04/2015 06:57 AM, yjin wrote: > An alternative is moving the definitions to a ".c" file, but I don't > think it will be fundamental different. > I know I am fixing a potential error which doesn't exist now, it seems > useless for the current upstream version, we can abandon my patch. But I > still think the current implementation adds unnecessary restrictions for > its users. I think that both dma_map_sg_chained and dma_unmap_sg_chained should go away. They were added to support chained scatterlists, but as far as I verified, dma_map_sg should handle that case as well. Kim, can you confirm this? Cristian S.