All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC V2 2/3] arm64/mm: Define arch_get_mappable_range()
Date: Tue, 01 Dec 2020 01:38:24 +0800	[thread overview]
Message-ID: <202012010154.fUYPC74K-lkp@intel.com> (raw)
In-Reply-To: <1606706992-26656-3-git-send-email-anshuman.khandual@arm.com>

[-- Attachment #1: Type: text/plain, Size: 2885 bytes --]

Hi Anshuman,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on v5.10-rc6]
[cannot apply to mmotm/master s390/features arm64/for-next/core hnaz-linux-mm/master next-20201130]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Anshuman-Khandual/mm-hotplug-Pre-validate-the-address-range-with-platform/20201130-113145
base:    b65054597872ce3aefbc6a666385eabdf9e288da
config: arm64-randconfig-r002-20201130 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project dfcf1acf13226be0f599a7ab6b395b66dc9545d6)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/7d8145ca97fc2f90d8378399cf1823cfd90049be
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Anshuman-Khandual/mm-hotplug-Pre-validate-the-address-range-with-platform/20201130-113145
        git checkout 7d8145ca97fc2f90d8378399cf1823cfd90049be
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> arch/arm64/mm/mmu.c:1447:14: warning: no previous prototype for function 'arch_get_mappable_range' [-Wmissing-prototypes]
   struct range arch_get_mappable_range(void)
                ^
   arch/arm64/mm/mmu.c:1447:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   struct range arch_get_mappable_range(void)
   ^
   static 
   1 warning generated.

vim +/arch_get_mappable_range +1447 arch/arm64/mm/mmu.c

  1446	
> 1447	struct range arch_get_mappable_range(void)
  1448	{
  1449		struct range memhp_range;
  1450	
  1451		/*
  1452		 * Linear mapping region is the range [PAGE_OFFSET..(PAGE_END - 1)]
  1453		 * accommodating both its ends but excluding PAGE_END. Max physical
  1454		 * range which can be mapped inside this linear mapping range, must
  1455		 * also be derived from its end points.
  1456		 */
  1457		memhp_range.start = __pa(_PAGE_OFFSET(vabits_actual));
  1458		memhp_range.end =  __pa(PAGE_END - 1);
  1459		return memhp_range;
  1460	}
  1461	

---
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: 32225 bytes --]

  parent reply	other threads:[~2020-11-30 17:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  3:29 [RFC V2 0/3] mm/hotplug: Pre-validate the address range with platform Anshuman Khandual
2020-11-30  3:29 ` Anshuman Khandual
2020-11-30  3:29 ` [RFC V2 1/3] mm/hotplug: Prevalidate the address range being added " Anshuman Khandual
2020-11-30  3:29   ` Anshuman Khandual
2020-12-02  5:10   ` kernel test robot
2020-12-02  9:20   ` David Hildenbrand
2020-12-02  9:20     ` David Hildenbrand
2020-12-02 12:15     ` Anshuman Khandual
2020-12-02 12:15       ` Anshuman Khandual
2020-11-30  3:29 ` [RFC V2 2/3] arm64/mm: Define arch_get_mappable_range() Anshuman Khandual
2020-11-30  3:29   ` Anshuman Khandual
2020-11-30  5:29   ` kernel test robot
2020-11-30 17:38   ` kernel test robot [this message]
2020-12-02  9:26   ` David Hildenbrand
2020-12-02  9:26     ` David Hildenbrand
2020-12-02 12:17     ` Anshuman Khandual
2020-12-02 12:17       ` Anshuman Khandual
2020-11-30  3:29 ` [RFC V2 3/3] s390/mm: " Anshuman Khandual
2020-11-30  3:29   ` Anshuman Khandual
2020-11-30  5:40   ` kernel test robot
2020-12-02 20:32   ` Heiko Carstens
2020-12-02 20:32     ` Heiko Carstens
2020-12-03  0:33     ` Anshuman Khandual
2020-12-03  0:33       ` Anshuman Khandual
2020-12-03 11:51       ` Heiko Carstens
2020-12-03 11:51         ` Heiko Carstens
2020-12-03 12:01         ` David Hildenbrand
2020-12-03 12:01           ` David Hildenbrand
2020-12-07  4:38           ` Anshuman Khandual
2020-12-07  4:38             ` Anshuman Khandual
2020-12-07  9:03             ` David Hildenbrand
2020-12-07  9:03               ` David Hildenbrand
2020-12-08  5:32               ` Anshuman Khandual
2020-12-08  5:32                 ` Anshuman Khandual
2020-12-08  8:38                 ` David Hildenbrand
2020-12-08  8:38                   ` David Hildenbrand
2020-12-02  6:44 ` [RFC V2 0/3] mm/hotplug: Pre-validate the address range with platform Anshuman Khandual
2020-12-02  6:44   ` Anshuman Khandual
2020-12-02 20:35 ` Heiko Carstens
2020-12-02 20:35   ` Heiko Carstens
2020-12-03  0:12   ` Anshuman Khandual
2020-12-03  0:12     ` Anshuman Khandual

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=202012010154.fUYPC74K-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.