From: Jakub Kicinski <kuba@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-sh@vger.kernel.org, linux-omap@vger.kernel.org,
linux-mm@kvack.org, linux-mips@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-fbdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
kunit-dev@googlegroups.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, bpf@vger.kernel.org,
amd-gfx@lists.freedesktop.org
Subject: Re: [linux-next:master] BUILD REGRESSION 1e1b28b936aed946122b4e0991e7144fdbbfd77e
Date: Mon, 16 May 2022 12:06:05 -0700 [thread overview]
Message-ID: <20220516120605.7a6bb562@kernel.org> (raw)
In-Reply-To: <6280f965.kTCPpIEVY9TwoNre%lkp@intel.com>
On Sun, 15 May 2022 21:00:21 +0800 kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 1e1b28b936aed946122b4e0991e7144fdbbfd77e Add linux-next specific files for 20220513
>
> Error/Warning reports:
>
> https://lore.kernel.org/linux-mm/202204181931.klAC6fWo-lkp@intel.com
> https://lore.kernel.org/linux-mm/202204291924.vTGZmerI-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205031017.4TwMan3l-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205041248.WgCwPcEV-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205122113.uLKzd3SZ-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205150051.3RzuooAG-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205150117.sd6HzBVm-lkp@intel.com
> https://lore.kernel.org/lkml/202205100617.5UUm3Uet-lkp@intel.com
> https://lore.kernel.org/llvm/202204210555.DNvfHvIb-lkp@intel.com
> https://lore.kernel.org/llvm/202205060132.uhqyUx1l-lkp@intel.com
> https://lore.kernel.org/llvm/202205120010.zWBednzM-lkp@intel.com
> https://lore.kernel.org/llvm/202205141122.qihFGUem-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> <command-line>: fatal error: ./include/generated/utsrelease.h: No such file or directory
> arch/arm/mach-versatile/versatile.c:56:14: warning: no previous prototype for function 'mmc_status' [-Wmissing-prototypes]
> arch/x86/kvm/pmu.h:20:32: warning: 'vmx_icl_pebs_cpu' defined but not used [-Wunused-const-variable=]
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:5102:7: warning: variable 'allow_lttpr_non_transparent_mode' set but not used [-Wunused-but-set-variable]
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:5147:6: warning: no previous prototype for function 'dp_parse_lttpr_mode' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1364:5: warning: no previous prototype for 'amdgpu_discovery_get_mall_info' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c:1983:6: warning: no previous prototype for function 'gfx_v11_0_rlc_stop' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/soc21.c:171:6: warning: no previous prototype for 'soc21_grbm_select' [-Wmissing-prototypes]
> drivers/gpu/drm/solomon/ssd130x-spi.c:154:35: warning: 'ssd130x_spi_table' defined but not used [-Wunused-const-variable=]
> drivers/hwmon/nct6775-platform.c:199:9: sparse: unsigned char
> drivers/hwmon/nct6775-platform.c:199:9: sparse: void
> drivers/video/fbdev/omap/hwa742.c:492:5: warning: no previous prototype for 'hwa742_update_window_async' [-Wmissing-prototypes]
> fs/buffer.c:2254:5: warning: stack frame size (2144) exceeds limit (1024) in 'block_read_full_folio' [-Wframe-larger-than]
> fs/ntfs/aops.c:378:12: warning: stack frame size (2224) exceeds limit (1024) in 'ntfs_read_folio' [-Wframe-larger-than]
> kernel/trace/fgraph.c:37:12: warning: no previous prototype for 'ftrace_enable_ftrace_graph_caller' [-Wmissing-prototypes]
> kernel/trace/fgraph.c:46:12: warning: no previous prototype for 'ftrace_disable_ftrace_graph_caller' [-Wmissing-prototypes]
Is this report CCed everywhere or there's a reason why netdev@ is CCed?
I'm trying to figure out we need to care and it's not obvious..
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: linux-hwmon@vger.kernel.org, linux-fbdev@vger.kernel.org,
kvm@vger.kernel.org, linux-sh@vger.kernel.org,
netdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-staging@lists.linux.dev, linux-mips@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
amd-gfx@lists.freedesktop.org, linux-kselftest@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-omap@vger.kernel.org, bpf@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kunit-dev@googlegroups.com
Subject: Re: [linux-next:master] BUILD REGRESSION 1e1b28b936aed946122b4e0991e7144fdbbfd77e
Date: Mon, 16 May 2022 12:06:05 -0700 [thread overview]
Message-ID: <20220516120605.7a6bb562@kernel.org> (raw)
In-Reply-To: <6280f965.kTCPpIEVY9TwoNre%lkp@intel.com>
On Sun, 15 May 2022 21:00:21 +0800 kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 1e1b28b936aed946122b4e0991e7144fdbbfd77e Add linux-next specific files for 20220513
>
> Error/Warning reports:
>
> https://lore.kernel.org/linux-mm/202204181931.klAC6fWo-lkp@intel.com
> https://lore.kernel.org/linux-mm/202204291924.vTGZmerI-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205031017.4TwMan3l-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205041248.WgCwPcEV-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205122113.uLKzd3SZ-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205150051.3RzuooAG-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205150117.sd6HzBVm-lkp@intel.com
> https://lore.kernel.org/lkml/202205100617.5UUm3Uet-lkp@intel.com
> https://lore.kernel.org/llvm/202204210555.DNvfHvIb-lkp@intel.com
> https://lore.kernel.org/llvm/202205060132.uhqyUx1l-lkp@intel.com
> https://lore.kernel.org/llvm/202205120010.zWBednzM-lkp@intel.com
> https://lore.kernel.org/llvm/202205141122.qihFGUem-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> <command-line>: fatal error: ./include/generated/utsrelease.h: No such file or directory
> arch/arm/mach-versatile/versatile.c:56:14: warning: no previous prototype for function 'mmc_status' [-Wmissing-prototypes]
> arch/x86/kvm/pmu.h:20:32: warning: 'vmx_icl_pebs_cpu' defined but not used [-Wunused-const-variable=]
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:5102:7: warning: variable 'allow_lttpr_non_transparent_mode' set but not used [-Wunused-but-set-variable]
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:5147:6: warning: no previous prototype for function 'dp_parse_lttpr_mode' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1364:5: warning: no previous prototype for 'amdgpu_discovery_get_mall_info' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c:1983:6: warning: no previous prototype for function 'gfx_v11_0_rlc_stop' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/soc21.c:171:6: warning: no previous prototype for 'soc21_grbm_select' [-Wmissing-prototypes]
> drivers/gpu/drm/solomon/ssd130x-spi.c:154:35: warning: 'ssd130x_spi_table' defined but not used [-Wunused-const-variable=]
> drivers/hwmon/nct6775-platform.c:199:9: sparse: unsigned char
> drivers/hwmon/nct6775-platform.c:199:9: sparse: void
> drivers/video/fbdev/omap/hwa742.c:492:5: warning: no previous prototype for 'hwa742_update_window_async' [-Wmissing-prototypes]
> fs/buffer.c:2254:5: warning: stack frame size (2144) exceeds limit (1024) in 'block_read_full_folio' [-Wframe-larger-than]
> fs/ntfs/aops.c:378:12: warning: stack frame size (2224) exceeds limit (1024) in 'ntfs_read_folio' [-Wframe-larger-than]
> kernel/trace/fgraph.c:37:12: warning: no previous prototype for 'ftrace_enable_ftrace_graph_caller' [-Wmissing-prototypes]
> kernel/trace/fgraph.c:46:12: warning: no previous prototype for 'ftrace_disable_ftrace_graph_caller' [-Wmissing-prototypes]
Is this report CCed everywhere or there's a reason why netdev@ is CCed?
I'm trying to figure out we need to care and it's not obvious..
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-sh@vger.kernel.org, linux-omap@vger.kernel.org,
linux-mm@kvack.org, linux-mips@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-fbdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
kunit-dev@googlegroups.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, bpf@vger.kernel.org,
amd-gfx@lists.freedesktop.org
Subject: Re: [linux-next:master] BUILD REGRESSION 1e1b28b936aed946122b4e0991e7144fdbbfd77e
Date: Mon, 16 May 2022 12:06:05 -0700 [thread overview]
Message-ID: <20220516120605.7a6bb562@kernel.org> (raw)
In-Reply-To: <6280f965.kTCPpIEVY9TwoNre%lkp@intel.com>
On Sun, 15 May 2022 21:00:21 +0800 kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 1e1b28b936aed946122b4e0991e7144fdbbfd77e Add linux-next specific files for 20220513
>
> Error/Warning reports:
>
> https://lore.kernel.org/linux-mm/202204181931.klAC6fWo-lkp@intel.com
> https://lore.kernel.org/linux-mm/202204291924.vTGZmerI-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205031017.4TwMan3l-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205041248.WgCwPcEV-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205122113.uLKzd3SZ-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205150051.3RzuooAG-lkp@intel.com
> https://lore.kernel.org/linux-mm/202205150117.sd6HzBVm-lkp@intel.com
> https://lore.kernel.org/lkml/202205100617.5UUm3Uet-lkp@intel.com
> https://lore.kernel.org/llvm/202204210555.DNvfHvIb-lkp@intel.com
> https://lore.kernel.org/llvm/202205060132.uhqyUx1l-lkp@intel.com
> https://lore.kernel.org/llvm/202205120010.zWBednzM-lkp@intel.com
> https://lore.kernel.org/llvm/202205141122.qihFGUem-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> <command-line>: fatal error: ./include/generated/utsrelease.h: No such file or directory
> arch/arm/mach-versatile/versatile.c:56:14: warning: no previous prototype for function 'mmc_status' [-Wmissing-prototypes]
> arch/x86/kvm/pmu.h:20:32: warning: 'vmx_icl_pebs_cpu' defined but not used [-Wunused-const-variable=]
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:5102:7: warning: variable 'allow_lttpr_non_transparent_mode' set but not used [-Wunused-but-set-variable]
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:5147:6: warning: no previous prototype for function 'dp_parse_lttpr_mode' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1364:5: warning: no previous prototype for 'amdgpu_discovery_get_mall_info' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c:1983:6: warning: no previous prototype for function 'gfx_v11_0_rlc_stop' [-Wmissing-prototypes]
> drivers/gpu/drm/amd/amdgpu/soc21.c:171:6: warning: no previous prototype for 'soc21_grbm_select' [-Wmissing-prototypes]
> drivers/gpu/drm/solomon/ssd130x-spi.c:154:35: warning: 'ssd130x_spi_table' defined but not used [-Wunused-const-variable=]
> drivers/hwmon/nct6775-platform.c:199:9: sparse: unsigned char
> drivers/hwmon/nct6775-platform.c:199:9: sparse: void
> drivers/video/fbdev/omap/hwa742.c:492:5: warning: no previous prototype for 'hwa742_update_window_async' [-Wmissing-prototypes]
> fs/buffer.c:2254:5: warning: stack frame size (2144) exceeds limit (1024) in 'block_read_full_folio' [-Wframe-larger-than]
> fs/ntfs/aops.c:378:12: warning: stack frame size (2224) exceeds limit (1024) in 'ntfs_read_folio' [-Wframe-larger-than]
> kernel/trace/fgraph.c:37:12: warning: no previous prototype for 'ftrace_enable_ftrace_graph_caller' [-Wmissing-prototypes]
> kernel/trace/fgraph.c:46:12: warning: no previous prototype for 'ftrace_disable_ftrace_graph_caller' [-Wmissing-prototypes]
Is this report CCed everywhere or there's a reason why netdev@ is CCed?
I'm trying to figure out we need to care and it's not obvious..
_______________________________________________
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:[~2022-05-16 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 13:00 [linux-next:master] BUILD REGRESSION 1e1b28b936aed946122b4e0991e7144fdbbfd77e kernel test robot
2022-05-15 13:00 ` kernel test robot
2022-05-15 13:00 ` [Intel-gfx] " kernel test robot
2022-05-15 13:00 ` kernel test robot
2022-05-16 19:06 ` Jakub Kicinski [this message]
2022-05-16 19:06 ` Jakub Kicinski
2022-05-16 19:06 ` Jakub Kicinski
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=20220516120605.7a6bb562@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bpf@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kunit-dev@googlegroups.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@intel.com \
--cc=netdev@vger.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.