public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Fengguang Wu <lkp@intel.com>
Cc: Sinan Kaya <okaya@codeaurora.org>,
	linux-arm-kernel@lists.infradead.org,
	Mark Rutland <mark.rutland@arm.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Vinod Koul <vinod.koul@intel.com>,
	jcm@redhat.com, timur@codeaurora.org,
	Kumar Gala <galak@codeaurora.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	kbuild-all@01.org, agross@codeaurora.org,
	dmaengine@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	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	[thread overview]
Message-ID: <4119660.BobUIRMK6T@wuerfel> (raw)
In-Reply-To: <20151111022103.GA29459@wfg-t540p.sh.intel.com>

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

  reply	other threads:[~2015-11-11  8:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1446958380-23298-1-git-send-email-okaya@codeaurora.org>
2015-11-08  4:52 ` [PATCH V3 1/4] dma: qcom_bam_dma: move to qcom directory Sinan Kaya
2015-11-08  5:02   ` Timur Tabi
2015-11-08  4:52 ` [PATCH V3 2/4] dma: add Qualcomm Technologies HIDMA management driver Sinan Kaya
2015-11-08  5:08   ` Timur Tabi
2015-11-09  2:17     ` Sinan Kaya
2015-11-09 18:25       ` Rob Herring
2015-11-10  4:57         ` Sinan Kaya
2015-11-08  9:32   ` kbuild test robot
2015-11-08  4:52 ` [PATCH V3 3/4] dmaselftest: add memcpy selftest support functions Sinan Kaya
2015-11-08  5:13   ` Timur Tabi
2015-11-09  2:46     ` Sinan Kaya
2015-11-09 13:48       ` Timur Tabi
2015-11-10  4:49         ` Sinan Kaya
2015-11-10 10:13           ` Arnd Bergmann
2015-11-08 20:09   ` Andy Shevchenko
2015-11-09  3:07     ` Sinan Kaya
2015-11-09  9:26       ` Andy Shevchenko
2015-11-10  4:55         ` Sinan Kaya
2015-11-10  4:59           ` Timur Tabi
2015-11-08  4:53 ` [PATCH V3 4/4] dma: add Qualcomm Technologies HIDMA channel driver Sinan Kaya
2015-11-08 19:13   ` kbuild test robot
2015-11-09  0:43     ` Sinan Kaya
2015-11-11  2:21       ` [kbuild-all] " Fengguang Wu
2015-11-11  8:42         ` Arnd Bergmann [this message]
2015-11-12  8:20           ` Fengguang Wu
2015-11-12 13:49             ` Arnd Bergmann
2015-11-08 20:47   ` Andy Shevchenko
2015-11-08 21:51     ` Sinan Kaya
2015-11-08 22:00       ` Andy Shevchenko
2015-11-09  0:31     ` Sinan Kaya
2015-11-09 18:19   ` Rob Herring
2015-11-10  4:44     ` Sinan Kaya

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=4119660.BobUIRMK6T@wuerfel \
    --to=arnd@arndb.de \
    --cc=agross@codeaurora.org \
    --cc=cov@codeaurora.org \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jcm@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=okaya@codeaurora.org \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=timur@codeaurora.org \
    --cc=vinod.koul@intel.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