From: kbuild test robot <lkp@intel.com>
To: Barry Song <song.bao.hua@hisilicon.com>,
hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com,
catalin.marinas@arm.com
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA
Date: Wed, 3 Jun 2020 15:18:58 +0800 [thread overview]
Message-ID: <202006031517.AYCbWIuo%lkp@intel.com> (raw)
In-Reply-To: <20200603024231.61748-2-song.bao.hua@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
Hi Barry,
I love your patch! Perhaps something to improve:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on linus/master v5.7]
[cannot apply to next-20200602]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CMA-for-ARM-server/20200603-104821
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: i386-randconfig-s002-20200602 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-244-g0ee050a8-dirty
# save the attached .config to linux build tree
make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/dma/contiguous.c:40:12: sparse: sparse: symbol 'dma_contiguous_pernuma_area' was not declared. Should it be static?
>> kernel/dma/contiguous.c:278:50: sparse: sparse: invalid access below 'dma_contiguous_pernuma_area' (-4 4)
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27963 bytes --]
[-- Attachment #3: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Barry Song <song.bao.hua@hisilicon.com>,
hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com,
catalin.marinas@arm.com
Cc: kbuild-all@lists.01.org, john.garry@huawei.com,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
iommu@lists.linux-foundation.org, Jonathan.Cameron@huawei.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA
Date: Wed, 3 Jun 2020 15:18:58 +0800 [thread overview]
Message-ID: <202006031517.AYCbWIuo%lkp@intel.com> (raw)
In-Reply-To: <20200603024231.61748-2-song.bao.hua@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
Hi Barry,
I love your patch! Perhaps something to improve:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on linus/master v5.7]
[cannot apply to next-20200602]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CMA-for-ARM-server/20200603-104821
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: i386-randconfig-s002-20200602 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-244-g0ee050a8-dirty
# save the attached .config to linux build tree
make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/dma/contiguous.c:40:12: sparse: sparse: symbol 'dma_contiguous_pernuma_area' was not declared. Should it be static?
>> kernel/dma/contiguous.c:278:50: sparse: sparse: invalid access below 'dma_contiguous_pernuma_area' (-4 4)
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27963 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA
Date: Wed, 03 Jun 2020 15:18:58 +0800 [thread overview]
Message-ID: <202006031517.AYCbWIuo%lkp@intel.com> (raw)
In-Reply-To: <20200603024231.61748-2-song.bao.hua@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
Hi Barry,
I love your patch! Perhaps something to improve:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on linus/master v5.7]
[cannot apply to next-20200602]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CMA-for-ARM-server/20200603-104821
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: i386-randconfig-s002-20200602 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-244-g0ee050a8-dirty
# save the attached .config to linux build tree
make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/dma/contiguous.c:40:12: sparse: sparse: symbol 'dma_contiguous_pernuma_area' was not declared. Should it be static?
>> kernel/dma/contiguous.c:278:50: sparse: sparse: invalid access below 'dma_contiguous_pernuma_area' (-4 4)
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 27963 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Barry Song <song.bao.hua@hisilicon.com>,
hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com,
catalin.marinas@arm.com
Cc: kbuild-all@lists.01.org, iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
Jonathan.Cameron@huawei.com, john.garry@huawei.com
Subject: Re: [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA
Date: Wed, 3 Jun 2020 15:18:58 +0800 [thread overview]
Message-ID: <202006031517.AYCbWIuo%lkp@intel.com> (raw)
In-Reply-To: <20200603024231.61748-2-song.bao.hua@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
Hi Barry,
I love your patch! Perhaps something to improve:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on linus/master v5.7]
[cannot apply to next-20200602]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CMA-for-ARM-server/20200603-104821
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: i386-randconfig-s002-20200602 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-244-g0ee050a8-dirty
# save the attached .config to linux build tree
make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/dma/contiguous.c:40:12: sparse: sparse: symbol 'dma_contiguous_pernuma_area' was not declared. Should it be static?
>> kernel/dma/contiguous.c:278:50: sparse: sparse: invalid access below 'dma_contiguous_pernuma_area' (-4 4)
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27963 bytes --]
next prev parent reply other threads:[~2020-06-03 7:19 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 2:42 [PATCH 0/3] support per-numa CMA for ARM server Barry Song
2020-06-03 2:42 ` Barry Song
2020-06-03 2:42 ` Barry Song
2020-06-03 2:42 ` [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA Barry Song
2020-06-03 2:42 ` Barry Song
2020-06-03 2:42 ` Barry Song
2020-06-03 6:55 ` kbuild test robot
2020-06-03 6:55 ` kbuild test robot
2020-06-03 6:55 ` kbuild test robot
2020-06-03 6:55 ` kbuild test robot
2020-06-03 7:18 ` kbuild test robot [this message]
2020-06-03 7:18 ` kbuild test robot
2020-06-03 7:18 ` kbuild test robot
2020-06-03 7:18 ` kbuild test robot
2020-06-03 7:18 ` [RFC PATCH] dma-direct: dma_contiguous_pernuma_area[] can be static kbuild test robot
2020-06-03 7:18 ` kbuild test robot
2020-06-03 7:18 ` kbuild test robot
2020-06-03 7:18 ` kbuild test robot
2020-06-04 11:36 ` [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA Dan Carpenter
2020-06-04 11:36 ` Dan Carpenter
2020-06-04 11:36 ` Dan Carpenter
2020-06-04 11:36 ` Dan Carpenter
2020-06-04 11:36 ` Dan Carpenter
2020-06-05 6:04 ` Song Bao Hua (Barry Song)
2020-06-05 6:04 ` Song Bao Hua (Barry Song)
2020-06-05 6:04 ` Song Bao Hua
2020-06-05 6:04 ` Song Bao Hua (Barry Song)
2020-06-05 8:57 ` Dan Carpenter
2020-06-05 8:57 ` Dan Carpenter
2020-06-05 8:57 ` Dan Carpenter
2020-06-05 8:57 ` Dan Carpenter
2020-06-05 8:57 ` Dan Carpenter
2020-06-06 3:46 ` [kbuild-all] " Philip Li
2020-06-06 3:46 ` Philip Li
2020-06-06 3:46 ` Philip Li
2020-06-06 3:46 ` [kbuild-all] " Philip Li
2020-06-06 3:46 ` Philip Li
2020-06-06 10:15 ` Song Bao Hua (Barry Song)
2020-06-06 10:15 ` Song Bao Hua (Barry Song)
2020-06-06 10:15 ` Song Bao Hua
2020-06-06 10:15 ` [kbuild-all] " Song Bao Hua (Barry Song)
2020-06-05 13:57 ` kernel test robot
2020-06-05 13:57 ` kernel test robot
2020-06-05 13:57 ` kernel test robot
2020-06-05 13:57 ` kernel test robot
2020-06-03 2:42 ` [PATCH 2/3] arm64: mm: reserve hugetlb CMA after numa_init Barry Song
2020-06-03 2:42 ` Barry Song
2020-06-03 2:42 ` Barry Song
2020-06-03 3:22 ` Roman Gushchin via iommu
2020-06-03 3:22 ` Roman Gushchin
2020-06-03 3:22 ` Roman Gushchin
2020-06-07 20:14 ` Matthias Brugger
2020-06-07 20:14 ` Matthias Brugger
2020-06-07 20:14 ` Matthias Brugger
2020-06-08 0:50 ` Song Bao Hua (Barry Song)
2020-06-08 0:50 ` Song Bao Hua (Barry Song)
2020-06-08 0:50 ` Song Bao Hua (Barry Song)
2020-06-09 15:33 ` Matthias Brugger
2020-06-09 15:33 ` Matthias Brugger
2020-06-09 15:33 ` Matthias Brugger
2020-06-03 2:42 ` [PATCH 3/3] arm64: mm: reserve per-numa " Barry Song
2020-06-03 2:42 ` Barry Song
2020-06-03 2:42 ` Barry Song
-- strict thread matches above, loose matches on Subject: below --
2020-06-04 7:17 [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA kernel test robot
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=202006031517.AYCbWIuo%lkp@intel.com \
--to=lkp@intel.com \
--cc=catalin.marinas@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=song.bao.hua@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.