From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [kbuild-all] [PATCH V3 4/4] dma: add Qualcomm Technologies HIDMA channel driver Date: Wed, 11 Nov 2015 09:42 +0100 Message-ID: <4119660.BobUIRMK6T@wuerfel> References: <201511090323.GmbQltpW%fengguang.wu@intel.com> <563FEC48.2010404@codeaurora.org> <20151111022103.GA29459@wfg-t540p.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <20151111022103.GA29459-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Fengguang Wu Cc: Sinan Kaya , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Mark Rutland , Pawel Moll , Ian Campbell , Vinod Koul , jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, Kumar Gala , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Rob Herring , kbuild-all-JC7UmRfGjtg@public.gmane.org, agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Dan Williams , linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cov-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org List-Id: linux-arm-msm@vger.kernel.org On Wednesday 11 November 2015 10:21:03 Fengguang Wu wrote: > Hi Sinan, > > Sorry please ignore this warning -- it's actually a problem specific > to the mn10300 arch. I'll disable such warning in mn10300 in future. I just tried to find what happened here. mn10300 appears to define the type based on the gcc version: #if __GNUC__ == 4 typedef unsigned int __kernel_size_t; typedef signed int __kernel_ssize_t; #else typedef unsigned long __kernel_size_t; typedef signed long __kernel_ssize_t; #endif while gcc defines it based on whether you are using a Linux targetted gcc or a bare-metal one: gcc/config/mn10300/linux.h:#undef SIZE_TYPE gcc/config/mn10300/mn10300.h:#undef SIZE_TYPE gcc/config/mn10300/mn10300.h:#define SIZE_TYPE "unsigned int" I can think of two reasons why it went wrong here: a) You are using gcc-5.x, and the check in the kernel should be ">=" rather than "==". We should probably fix that regardless b) You are using a bare-metal gcc rather than a Linux version. I couldn't find an mn10300 gcc on kernel.org, which one do you use? Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752137AbbKKIm4 (ORCPT ); Wed, 11 Nov 2015 03:42:56 -0500 Received: from mout.kundenserver.de ([212.227.126.187]:52856 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751820AbbKKImy (ORCPT ); Wed, 11 Nov 2015 03:42:54 -0500 From: Arnd Bergmann To: Fengguang Wu Cc: Sinan Kaya , linux-arm-kernel@lists.infradead.org, Mark Rutland , Pawel Moll , Ian Campbell , Vinod Koul , jcm@redhat.com, timur@codeaurora.org, Kumar Gala , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Rob Herring , kbuild-all@01.org, agross@codeaurora.org, dmaengine@vger.kernel.org, Dan Williams , linux-arm-msm@vger.kernel.org, cov@codeaurora.org Subject: Re: [kbuild-all] [PATCH V3 4/4] dma: add Qualcomm Technologies HIDMA channel driver Date: Wed, 11 Nov 2015 09:42 +0100 Message-ID: <4119660.BobUIRMK6T@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20151111022103.GA29459@wfg-t540p.sh.intel.com> References: <201511090323.GmbQltpW%fengguang.wu@intel.com> <563FEC48.2010404@codeaurora.org> <20151111022103.GA29459@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:DHqKJK5yOQXUQJrdbZDaXYP/IxQ07uuVpeaXtIwgadcAgtEAnBu bN03EfudhXs11QOUL/OPHzAPz1oYR6sdkMjd6OIm8dY+X0QmdObNjUJ7ObAANpdmPzQnCyE 8QYGqg5ZPK6gTfZ0ItWFOCPiJtigTDKeL7dE+CwPkatAkCHolmkcTTIAd6t2FxUWG2W9udA /P0q/Z+7dK5OuY3oOnxvw== X-UI-Out-Filterresults: notjunk:1;V01:K0:sBjs5iX0li4=:BbMfg5wUayAfRd6mTS0O/F eJpmaY8v8kQPfbOwMNHVaqR6S+YAu6q2uYLeTtsUmzgCqlpn6G/Bh1QutEVyjq7sKbNO0v+L/ WrKhtZvbNEk/yS7yYeRPDVRcTV4FDHwpJeYOpUJOmCLb8E1kmN9TkrkgsMEWjtWJCTbiWQqB2 eaNhp1VGHovII7YVu5nzMbZQ8RlVIIChqNA49LIeAF0d3CA/+LgVxbsCgdRx9ysujFbC8hezM 7HCh9ugbGOta9w2dAEHiayXMcQJ5LNiQ4KQiC92vnE6Nb73chl9vAkogDeMU8d3AiGWqkFHPU sCBO1bngXW/kG8QytPH2fS6MkrZEmCqPB77ZRvqcRSdX4r8MzALiiRQhun5mbDAUDbBRAsi3V t0xhWAXaxmwuNjIrtvPbnMcjOwEa+N+UvbhtFetWLuvpo1BB2LtwIV0jORcb0jhyL2vlk45ln kO2wMPfsjP2EH8c9pKvSDuGJAtftxemWpAj7u2zqwIfqhIZoA6z25+d0fDBNQj/dYASo20LVZ mtm8TQoFrtlJXp4RfgndJXn3l8kwnl/cAONPWtGm54h5Nep/Embfb/Wiug0xAMzjNy6jeThAw KdUVlygEU13wz1EFcjx2maQbDUFTSMQq48xi1g4vwnicg8Ea/mgDRKSSPJjV7qsVjKxA+rrwh b5CREidc7aumkv6muXBKETQ2Bm2WNsU89JlPzDZFyTO2Kvqg46MWKK7eCpKxtaltqVb6nbFWp EpHMZ5tfsRkAcIwv Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 11 November 2015 10:21:03 Fengguang Wu wrote: > Hi Sinan, > > Sorry please ignore this warning -- it's actually a problem specific > to the mn10300 arch. I'll disable such warning in mn10300 in future. I just tried to find what happened here. mn10300 appears to define the type based on the gcc version: #if __GNUC__ == 4 typedef unsigned int __kernel_size_t; typedef signed int __kernel_ssize_t; #else typedef unsigned long __kernel_size_t; typedef signed long __kernel_ssize_t; #endif while gcc defines it based on whether you are using a Linux targetted gcc or a bare-metal one: gcc/config/mn10300/linux.h:#undef SIZE_TYPE gcc/config/mn10300/mn10300.h:#undef SIZE_TYPE gcc/config/mn10300/mn10300.h:#define SIZE_TYPE "unsigned int" I can think of two reasons why it went wrong here: a) You are using gcc-5.x, and the check in the kernel should be ">=" rather than "==". We should probably fix that regardless b) You are using a bare-metal gcc rather than a Linux version. I couldn't find an mn10300 gcc on kernel.org, which one do you use? Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Wed, 11 Nov 2015 09:42 +0100 Subject: [kbuild-all] [PATCH V3 4/4] dma: add Qualcomm Technologies HIDMA channel driver In-Reply-To: <20151111022103.GA29459@wfg-t540p.sh.intel.com> References: <201511090323.GmbQltpW%fengguang.wu@intel.com> <563FEC48.2010404@codeaurora.org> <20151111022103.GA29459@wfg-t540p.sh.intel.com> Message-ID: <4119660.BobUIRMK6T@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wednesday 11 November 2015 10:21:03 Fengguang Wu wrote: > Hi Sinan, > > Sorry please ignore this warning -- it's actually a problem specific > to the mn10300 arch. I'll disable such warning in mn10300 in future. I just tried to find what happened here. mn10300 appears to define the type based on the gcc version: #if __GNUC__ == 4 typedef unsigned int __kernel_size_t; typedef signed int __kernel_ssize_t; #else typedef unsigned long __kernel_size_t; typedef signed long __kernel_ssize_t; #endif while gcc defines it based on whether you are using a Linux targetted gcc or a bare-metal one: gcc/config/mn10300/linux.h:#undef SIZE_TYPE gcc/config/mn10300/mn10300.h:#undef SIZE_TYPE gcc/config/mn10300/mn10300.h:#define SIZE_TYPE "unsigned int" I can think of two reasons why it went wrong here: a) You are using gcc-5.x, and the check in the kernel should be ">=" rather than "==". We should probably fix that regardless b) You are using a bare-metal gcc rather than a Linux version. I couldn't find an mn10300 gcc on kernel.org, which one do you use? Arnd