From: kbuild test robot <lkp@intel.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: kbuild-all@01.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
daniel.vetter@ffwll.ch, robdclark@gmail.com, treding@nvidia.com,
sumit.semwal@linaro.org, tom.cooksey@arm.com,
daniel.stone@collabora.com,
linux-security-module@vger.kernel.org,
xiaoquan.li@vivantecorp.com, tom.gall@linaro.org,
linaro-mm-sig@lists.linaro.org,
Benjamin Gaignard <benjamin.gaignard@linaro.org>
Subject: Re: [PATCH v4 2/2] SMAF: add CMA allocator
Date: Mon, 5 Oct 2015 18:50:47 +0800 [thread overview]
Message-ID: <201510051847.pHUoDbfg%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444039898-7927-3-git-send-email-benjamin.gaignard@linaro.org>
Hi Benjamin,
[auto build test WARNING on v4.3-rc4 -- if it's inappropriate base, please ignore]
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/smaf/smaf-cma.c:178:23: sparse: symbol 'smaf_cma' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2015-10-05 10:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 10:11 [PATCH v4 0/2] RFC: Secure Memory Allocation Framework Benjamin Gaignard
2015-10-05 10:11 ` [PATCH v4 1/2] create SMAF module Benjamin Gaignard
2015-10-05 22:02 ` kbuild test robot
2015-10-06 1:58 ` Laura Abbott
2015-10-06 8:56 ` Benjamin Gaignard
2015-10-05 10:11 ` [PATCH v4 2/2] SMAF: add CMA allocator Benjamin Gaignard
2015-10-05 10:50 ` kbuild test robot [this message]
2015-10-05 10:50 ` [RFC PATCH] SMAF: smaf_cma can be static kbuild test robot
2015-10-05 11:50 ` [PATCH v4 2/2] SMAF: add CMA allocator kbuild test robot
2015-10-06 2:07 ` [PATCH v4 0/2] RFC: Secure Memory Allocation Framework Laura Abbott
2015-10-06 7:03 ` Benjamin Gaignard
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=201510051847.pHUoDbfg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=benjamin.gaignard@linaro.org \
--cc=daniel.stone@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=tom.cooksey@arm.com \
--cc=tom.gall@linaro.org \
--cc=treding@nvidia.com \
--cc=xiaoquan.li@vivantecorp.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;
as well as URLs for NNTP newsgroup(s).