From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
kexec@lists.infradead.org, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
Date: Fri, 17 Nov 2023 08:55:44 +0800 [thread overview]
Message-ID: <ZVa6EDP8EI2jWhQL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202311160022.QM6xJYSy-lkp@intel.com>
On 11/16/23 at 12:58am, kernel test robot wrote:
> Hi Baoquan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on tip/x86/core powerpc/next powerpc/fixes linus/master v6.7-rc1 next-20231115]
> [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#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Baoquan-He/kexec_file-add-kexec_file-flag-to-control-debug-printing/20231114-234003
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> patch link: https://lore.kernel.org/r/20231114153253.241262-5-bhe%40redhat.com
> patch subject: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
> config: arm64-randconfig-001-20231115 (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202311160022.QM6xJYSy-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> arch/arm64/kernel/machine_kexec.c: In function '_kexec_image_info':
> >> arch/arm64/kernel/machine_kexec.c:35:23: warning: unused variable 'i' [-Wunused-variable]
> 35 | unsigned long i;
> | ^
Yes, this is an obvious one missed, will fix and update in new post,
thanks.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
kexec@lists.infradead.org, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
Date: Fri, 17 Nov 2023 08:55:44 +0800 [thread overview]
Message-ID: <ZVa6EDP8EI2jWhQL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202311160022.QM6xJYSy-lkp@intel.com>
On 11/16/23 at 12:58am, kernel test robot wrote:
> Hi Baoquan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on tip/x86/core powerpc/next powerpc/fixes linus/master v6.7-rc1 next-20231115]
> [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#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Baoquan-He/kexec_file-add-kexec_file-flag-to-control-debug-printing/20231114-234003
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> patch link: https://lore.kernel.org/r/20231114153253.241262-5-bhe%40redhat.com
> patch subject: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
> config: arm64-randconfig-001-20231115 (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202311160022.QM6xJYSy-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> arch/arm64/kernel/machine_kexec.c: In function '_kexec_image_info':
> >> arch/arm64/kernel/machine_kexec.c:35:23: warning: unused variable 'i' [-Wunused-variable]
> 35 | unsigned long i;
> | ^
Yes, this is an obvious one missed, will fix and update in new post,
thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
kexec@lists.infradead.org, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
Date: Fri, 17 Nov 2023 08:55:44 +0800 [thread overview]
Message-ID: <ZVa6EDP8EI2jWhQL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202311160022.QM6xJYSy-lkp@intel.com>
On 11/16/23 at 12:58am, kernel test robot wrote:
> Hi Baoquan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on tip/x86/core powerpc/next powerpc/fixes linus/master v6.7-rc1 next-20231115]
> [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#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Baoquan-He/kexec_file-add-kexec_file-flag-to-control-debug-printing/20231114-234003
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> patch link: https://lore.kernel.org/r/20231114153253.241262-5-bhe%40redhat.com
> patch subject: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
> config: arm64-randconfig-001-20231115 (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202311160022.QM6xJYSy-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> arch/arm64/kernel/machine_kexec.c: In function '_kexec_image_info':
> >> arch/arm64/kernel/machine_kexec.c:35:23: warning: unused variable 'i' [-Wunused-variable]
> 35 | unsigned long i;
> | ^
Yes, this is an obvious one missed, will fix and update in new post,
thanks.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-parisc@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
Date: Fri, 17 Nov 2023 08:55:44 +0800 [thread overview]
Message-ID: <ZVa6EDP8EI2jWhQL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202311160022.QM6xJYSy-lkp@intel.com>
On 11/16/23 at 12:58am, kernel test robot wrote:
> Hi Baoquan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on tip/x86/core powerpc/next powerpc/fixes linus/master v6.7-rc1 next-20231115]
> [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#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Baoquan-He/kexec_file-add-kexec_file-flag-to-control-debug-printing/20231114-234003
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> patch link: https://lore.kernel.org/r/20231114153253.241262-5-bhe%40redhat.com
> patch subject: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
> config: arm64-randconfig-001-20231115 (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202311160022.QM6xJYSy-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> arch/arm64/kernel/machine_kexec.c: In function '_kexec_image_info':
> >> arch/arm64/kernel/machine_kexec.c:35:23: warning: unused variable 'i' [-Wunused-variable]
> 35 | unsigned long i;
> | ^
Yes, this is an obvious one missed, will fix and update in new post,
thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
kexec@lists.infradead.org, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
Date: Fri, 17 Nov 2023 08:55:44 +0800 [thread overview]
Message-ID: <ZVa6EDP8EI2jWhQL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202311160022.QM6xJYSy-lkp@intel.com>
On 11/16/23 at 12:58am, kernel test robot wrote:
> Hi Baoquan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on tip/x86/core powerpc/next powerpc/fixes linus/master v6.7-rc1 next-20231115]
> [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#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Baoquan-He/kexec_file-add-kexec_file-flag-to-control-debug-printing/20231114-234003
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> patch link: https://lore.kernel.org/r/20231114153253.241262-5-bhe%40redhat.com
> patch subject: [PATCH 4/7] kexec_file, arm64: print out debugging message if required
> config: arm64-randconfig-001-20231115 (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231116/202311160022.QM6xJYSy-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202311160022.QM6xJYSy-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> arch/arm64/kernel/machine_kexec.c: In function '_kexec_image_info':
> >> arch/arm64/kernel/machine_kexec.c:35:23: warning: unused variable 'i' [-Wunused-variable]
> 35 | unsigned long i;
> | ^
Yes, this is an obvious one missed, will fix and update in new post,
thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-17 0:56 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 15:32 [PATCH 0/7] kexec_file: print out debugging message if required Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` [PATCH 1/7] kexec_file: add kexec_file flag to control debug printing Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 16:03 ` Joe Perches
2023-11-14 16:03 ` Joe Perches
2023-11-14 16:03 ` Joe Perches
2023-11-14 16:03 ` Joe Perches
2023-11-14 16:03 ` Joe Perches
2023-11-15 0:58 ` Baoquan He
2023-11-15 0:58 ` Baoquan He
2023-11-15 0:58 ` Baoquan He
2023-11-15 0:58 ` Baoquan He
2023-11-15 0:58 ` Baoquan He
2023-11-15 12:51 ` [PATCH v2 " Baoquan He
2023-11-15 12:51 ` Baoquan He
2023-11-15 12:51 ` Baoquan He
2023-11-15 12:51 ` Baoquan He
2023-11-15 12:51 ` Baoquan He
2023-11-14 15:32 ` [PATCH 2/7] kexec_file: print out debugging message if required Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-15 21:04 ` kernel test robot
2023-11-15 21:04 ` kernel test robot
2023-11-15 21:04 ` kernel test robot
2023-11-15 21:04 ` kernel test robot
2023-11-15 21:04 ` kernel test robot
2023-11-17 9:14 ` Baoquan He
2023-11-17 9:14 ` Baoquan He
2023-11-17 9:14 ` Baoquan He
2023-11-17 9:14 ` Baoquan He
2023-11-17 9:14 ` Baoquan He
2023-11-17 9:37 ` Liu, Yujie
2023-11-17 9:37 ` Liu, Yujie
2023-11-17 9:37 ` Liu, Yujie
2023-11-17 9:37 ` Liu, Yujie
2023-11-17 9:37 ` Liu, Yujie
2023-11-17 14:01 ` bhe
2023-11-17 14:01 ` bhe
2023-11-17 14:01 ` bhe
2023-11-17 14:01 ` bhe
2023-11-17 14:01 ` bhe
2023-11-23 13:49 ` bhe
2023-11-23 13:49 ` bhe
2023-11-23 13:49 ` bhe
2023-11-23 13:49 ` bhe
2023-11-23 13:49 ` bhe
2023-11-23 15:41 ` Nathan Chancellor
2023-11-23 15:41 ` Nathan Chancellor
2023-11-23 15:41 ` Nathan Chancellor
2023-11-23 15:41 ` Nathan Chancellor
2023-11-23 15:41 ` Nathan Chancellor
2023-11-24 1:56 ` bhe
2023-11-24 1:56 ` bhe
2023-11-24 1:56 ` bhe
2023-11-24 1:56 ` bhe
2023-11-24 1:56 ` bhe
2023-11-24 1:18 ` Yujie Liu
2023-11-24 1:18 ` Yujie Liu
2023-11-24 1:18 ` Yujie Liu
2023-11-24 1:18 ` Yujie Liu
2023-11-24 1:18 ` Yujie Liu
2023-11-24 1:57 ` bhe
2023-11-24 1:57 ` bhe
2023-11-24 1:57 ` bhe
2023-11-24 1:57 ` bhe
2023-11-24 1:57 ` bhe
2023-11-15 21:57 ` kernel test robot
2023-11-15 21:57 ` kernel test robot
2023-11-15 21:57 ` kernel test robot
2023-11-15 21:57 ` kernel test robot
2023-11-15 21:57 ` kernel test robot
2023-11-17 8:21 ` Baoquan He
2023-11-17 8:21 ` Baoquan He
2023-11-17 8:21 ` Baoquan He
2023-11-17 8:21 ` Baoquan He
2023-11-17 8:21 ` Baoquan He
2023-11-14 15:32 ` [PATCH 3/7] kexec_file, x86: " Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` [PATCH 4/7] kexec_file, arm64: " Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-15 16:58 ` kernel test robot
2023-11-15 16:58 ` kernel test robot
2023-11-15 16:58 ` kernel test robot
2023-11-15 16:58 ` kernel test robot
2023-11-15 16:58 ` kernel test robot
2023-11-17 0:55 ` Baoquan He [this message]
2023-11-17 0:55 ` Baoquan He
2023-11-17 0:55 ` Baoquan He
2023-11-17 0:55 ` Baoquan He
2023-11-17 0:55 ` Baoquan He
2023-11-14 15:32 ` [PATCH 5/7] kexec_file, ricv: " Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` [PATCH 6/7] kexec_file, power: " Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` [PATCH 7/7] kexec_file, parisc: " Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
2023-11-14 15:32 ` Baoquan He
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=ZVa6EDP8EI2jWhQL@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@kernel.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.