Re: arch/x86/um/user-offsets.c:8:24: fatal error: asm/ptrace.h: No such file or directory

On Fri, Mar 18, 2016 at 12:22:25PM +0900, Krzysztof Kozlowski wrote: > On 18.03.2016 12:19, Philip Li wrote: > > On Mon, Mar 14, 2016 at 09:53:06AM +0900, Krzysztof Kozlowski wrote: > >> On Sun, Mar 13, 2016 at 7:45 AM, kbuild test robot > >> <fengguang...

Re: arch/x86/um/user-offsets.c:8:24: fatal error: asm/ptrace.h: No such file or directory

On Mon, Mar 14, 2016 at 09:53:06AM +0900, Krzysztof Kozlowski wrote: > On Sun, Mar 13, 2016 at 7:45 AM, kbuild test robot > wrote: > > Hi Al, > > > > FYI, the error/warning still remains. > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git >

Re: arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer'

On Mon, Apr 18, 2016 at 06:52:57PM +0300, Max Filippov wrote: > Hi Fengguang, > > On Mon, Apr 18, 2016 at 6:29 PM, kbuild test robot > wrote: > > FYI, the error/warning still remains. > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > >

Re: /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_set_encrypt_key does not evaluate to a constant

On Mon, Apr 18, 2016 at 05:08:41PM +0200, Oleg Nesterov wrote: > On 04/17, kbuild test robot wrote: > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce > > commit:

Re: [PATCH] bpf: avoid warning for wrong pointer cast

On Tue, Apr 19, 2016 at 10:33:34AM +0800, Fengguang Wu wrote: > Hi Alexei, > > On Sat, Apr 16, 2016 at 05:47:42PM -0700, Alexei Starovoitov wrote: > > On Sat, Apr 16, 2016 at 10:29:33PM +0200, Arnd Bergmann wrote: > > > Two new functions in bpf contain a cast from a 'u64' to a > > > pointer. This

Re: [PATCH 1/2] clk: sunxi: add predivider handling for factors clock

On Sun, Apr 17, 2016 at 11:53:47AM +0800, Vishnu Patekar wrote: > Both of these patches in series has to be applied at the same time. > I think this is the reason, it fails. hi Xiaolong, would you help do a check whether we apply the patches in correct sequence for this case? > On 17 Apr 2016

Re: [PATCH v5 6/6] crypto: AF_ALG - add support for key_id

On Fri, Apr 15, 2016 at 02:32:47PM -0700, Tadeusz Struk wrote: > On 04/15/2016 02:32 PM, kbuild test robot wrote: > > Hi Tadeusz, > > > > [auto build test ERROR on cryptodev/master] > > [also build test ERROR on v4.6-rc3 next-20160415] > > [if your patch is applied to the wrong git tree, please

Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'

On Mon, Feb 13, 2017 at 09:27:59AM +0530, Viresh Kumar wrote: > On 13-02-17, 11:41, Philip Li wrote: > > on the other side, this is a build issue from randconfig, looks the failure > > exists on linus/master > > head 1ce4284, and caused by 655c9df commit. Not sure whether y

Re: drivers/base/power/opp/core.c:1901:6: error: redefinition of 'dev_pm_opp_remove_table'

On Mon, Feb 13, 2017 at 10:40:53AM +, Sudeep Holla wrote: > On Sun, Feb 12, 2017 at 9:09 PM, kbuild test robot > wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head: 1ce42845f987e92eabfc6e026d44d826c25c74a5 > >

Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'

On Mon, Feb 13, 2017 at 09:04:55AM +0530, Viresh Kumar wrote: > On 13-02-17, 11:35, Philip Li wrote: > > On Mon, Feb 13, 2017 at 08:43:38AM +0530, Viresh Kumar wrote: > > > On 13-02-17, 03:35, kbuild test robot wrote: > > > > tree: > > > > https

Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'

On Mon, Feb 13, 2017 at 08:43:38AM +0530, Viresh Kumar wrote: > On 13-02-17, 03:35, kbuild test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head: 1ce42845f987e92eabfc6e026d44d826c25c74a5 > > commit:

Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f

On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: > On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot > wrote: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge > >

Re: [kbuild-all] [PATCH RT] usb: Use _nort in usb_hcd_pci_remove

On Tue, Apr 25, 2017 at 08:01:54AM -0400, Steven Rostedt wrote: > On Tue, 25 Apr 2017 13:26:41 +0800 > kbuild test robot wrote: > > > Hi Nate, > > > > [auto build test ERROR on usb/usb-testing] > > [also build test ERROR on v4.11-rc8 next-20170424] > > [if your patch is applied

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

On Sun, Sep 17, 2017 at 08:31:56AM -0700, Linus Torvalds wrote: > Fengguang, > it looks like the kernel build robot _only_ tests the actual rc > kernels, and doesn't bisect down where the error started. hi Linus, the robot will also bisect down the error if issue is found on linus repo. The

[0-Day CI notification] 0-Day kernel test service will be shut down from Sep 30 3PM to Oct 5

Hi all, this is Philip who maintains the 0-Day kernel test service. Thanks for subscribing to 0-Day kernel testing. We will have lab power down from Oct 1 to Oct 5, so that the service will be shut down from Asia Pacific Time Sep 30 3PM and will recover from Oct 6 as soon as we can. Sorry for any

Re: [linus:master] BUILD REGRESSION 68abbe729567cef128b2c2141f2ed2567f3b8372

On Fri, Jun 08, 2018 at 08:48:29AM -0700, Linus Torvalds wrote: > On Fri, Jun 8, 2018 at 8:12 AM kbuild test robot wrote: > > > > arch/sh/include/asm/io.h:246:32: warning: cast to pointer from integer of > > different size [-Wint-to-pointer-cast] > > arch/x86/net/bpf_jit_comp32.c:2449 do_jit()

Re: [linus:master] BUILD REGRESSION 68abbe729567cef128b2c2141f2ed2567f3b8372

On Sat, Jun 09, 2018 at 08:29:17AM +0800, Philip Li wrote: > On Fri, Jun 08, 2018 at 08:48:29AM -0700, Linus Torvalds wrote: > > On Fri, Jun 8, 2018 at 8:12 AM kbuild test robot wrote: > > > > > > arch/sh/include/asm/io.h:246:32: warning: cast to pointer from integ

Re: [kbuild-all] [PATCH v2 1/3] kbuild: use 'include' directive to load auto.conf from top Makefile

On Sun, Jun 24, 2018 at 05:56:24PM +0900, Masahiro Yamada wrote: > Hi. > > 2018-06-24 3:59 GMT+09:00 kbuild test robot : > > Hi Masahiro, > > > > I love your patch! Yet something to improve: > > > > [auto build test ERROR on kbuild/for-next] > > [also build test ERROR on v4.18-rc1 next-20180622]

Re: [PATCH kernel-tests] ignore compiler errors

applied On Mon, Dec 25, 2017 at 07:53:32PM +0800, Fengguang Wu wrote: > This looks more like some odd compiler regression than a kernel one. > >Linus > > The original report is: > > To: Linus Torvalds > Cc: LKML

[0-Day CI notification] 0-Day CI test service will be unavailable from Sep 30 to Oct 8

Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for subscribing to the service. We will have site level power down during China national holiday, so the service will be unavailable from Asia Pacific Time Sep 30 5PM to Oct 8 5PM. We will recover it as soon as we can. Sorry

[0-Day CI notification] 0-Day kernel test service will be shut down from Sep 30 3PM to Oct 5

Hi all, this is Philip who maintains the 0-Day kernel test service. Thanks for subscribing to 0-Day kernel testing. We will have lab power down from Oct 1 to Oct 5, so that the service will be shut down from Asia Pacific Time Sep 30 3PM and will recover from Oct 6 as soon as we can. Sorry for any

Re: [PATCH kernel-tests] ignore compiler errors

applied On Mon, Dec 25, 2017 at 07:53:32PM +0800, Fengguang Wu wrote: > This looks more like some odd compiler regression than a kernel one. > >Linus > > The original report is: > > To: Linus Torvalds > Cc: LKML > Subject: [linus:master] BUILD REGRESSION >

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

On Sun, Sep 17, 2017 at 08:31:56AM -0700, Linus Torvalds wrote: > Fengguang, > it looks like the kernel build robot _only_ tests the actual rc > kernels, and doesn't bisect down where the error started. hi Linus, the robot will also bisect down the error if issue is found on linus repo. The

Re: [kbuild-all] Re: [PATCH] mm: memcg/slab: fix slab statistics in !SMP configuration

On Thu, Oct 01, 2020 at 05:55:59PM -0700, Roman Gushchin wrote: > On Fri, Oct 02, 2020 at 08:08:40AM +0800, kbuild test robot wrote: > > Hi Roman, > > > > Thank you for the patch! Yet something to improve: > > > > [auto build test ERROR on mmotm/master] > > It's a bogus error, the patch was

Re: [kbuild-all] Re: [PATCH v5 03/15] misc: bcm-vk: add autoload support

On Thu, Oct 01, 2020 at 10:48:08AM -0700, Scott Branden wrote: > > > On 2020-09-30 9:07 p.m., kernel test robot wrote: > > Hi Scott, > > > > I love your patch! Yet something to improve: > > > > [auto build test ERROR on char-misc/char-misc-testing] > > [also build test ERROR on soc/for-next

Re: [PATCH 4/5] clk: qcom: Add SDM660 GPU Clock Controller (GPUCC) driver

On Wed, Sep 30, 2020 at 11:58:50PM +0200, AngeloGioacchino Del Regno wrote: > The kernel test robot is wrong: this commit builds fine by Thanks for the info and sorry for the wrong report. Currently it is hard to detect the base in this case automatically, if possible, we recommend to use --base

Re: [perf report] 977f739b71: perf-test.skid_test.round2.MEM_LOAD_L3_MISS_RETIRED.LOCAL_DRAM_dtlb_withou t_NMI_fixed_period.fail

On Wed, Sep 30, 2020 at 02:41:07PM +0200, Michael Petlan wrote: > Hello. To me, it looks rather a random failure. Is it actually reproducible > and proven that the patch has caused it? The patch doesn't seem to cause thanks for the input, we will look into this and provide update. Now since we are

Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332

On Thu, Sep 17, 2020 at 10:00:44AM +0200, Borislav Petkov wrote: > On Thu, Sep 17, 2020 at 03:36:20PM +0800, Philip Li wrote: > > The 2nd type is this one, which is a summarized report of head > > to provide an overview. Most of time, repo owner can receive the > > bisecte

Re: [MPTCP] Re: [selftests] f2ff7f11f9: WARNING:suspicious_RCU_usage

On Tue, Oct 27, 2020 at 04:07:28PM +0100, Matthieu Baerts wrote: > Hi all, > > On 27/10/2020 14:16, kernel test robot wrote: > > Greeting, > > > > FYI, we noticed the following commit (built with gcc-9): > > > > commit: f2ff7f11f9a74842245db52d685bf9bc7ac2c4b1 ("selftests: mptcp: add > >

Re: [kbuild-all] Re: [PATCH 1/3] Add TX sending hardware timestamp.

On Thu, Dec 10, 2020 at 12:41:32PM +, Geva, Erez wrote: > > On 10/12/2020 04:11, kernel test robot wrote: > > Hi Erez, > > > > Thank you for the patch! Yet something to improve: > > > Thanks for the robot, > as we rarely use clang for kernel. It is very helpful. > > > [auto build test

Re: [kbuild-all] Re: ERROR: "snd_soc_new_ac97_component" undefined!

On Thu, Dec 10, 2020 at 04:16:17PM -0800, Randy Dunlap wrote: > On 12/6/20 10:11 AM, kernel test robot wrote: > > Hi Geert, > > > > First bad commit (maybe != root cause): > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head:

Re: [kbuild-all] drivers/clocksource/timer-clint.c:72:24: sparse: sparse: cast removes address space '__iomem' of expression

On Thu, Dec 24, 2020 at 04:11:17PM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 58cf05f597b03a8212d9ecf2c79ee046d3ee8ad9 > commit: 2ac6795fcc085e8d03649f1bbd0d70aaff612cad clocksource/drivers: Add > CLINT timer

Re: [kbuild-all] Re: [linux-next:master 13538/13785] /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'

On Sat, Dec 19, 2020 at 08:56:06AM +0100, Pavel Machek wrote: > Crazy robot, stop spamming. This report is obviously bogus, yet, you > sent me 5 copies. Thanks Pavel for input, sorry for the false positive. It tries to bisect error like below (the new error), but it may be related to assember

Re: [kbuild-all] Re: [linux-next:master 13538/13785] /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'

On Sat, Dec 19, 2020 at 06:28:20PM +0800, Philip Li wrote: > On Sat, Dec 19, 2020 at 08:56:06AM +0100, Pavel Machek wrote: > > Crazy robot, stop spamming. This report is obviously bogus, yet, you > > sent me 5 copies. > Thanks Pavel for input, sorry for the false positive. It

Re: [kbuild-all] Re: [linux-next:master 13538/13785] /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'

On Sat, Dec 19, 2020 at 02:15:28PM +0100, Pavel Machek wrote: > Hi! > > > > > Crazy robot, stop spamming. This report is obviously bogus, yet, you > > > > sent me 5 copies. > > > Thanks Pavel for input, sorry for the false positive. It tries to > > > bisect error like below (the new error), but

Re: [Build fail] i386 & nvdimm is unhappy

On Thu, Oct 29, 2020 at 03:52:42PM -0700, Dan Williams wrote: > On Thu, Oct 29, 2020 at 3:44 PM Thomas Gleixner wrote: > > > > Dan, > > > > x86 32bit build fails with the config below with this: > > > > ERROR: modpost: "phys_to_target_node" [drivers/nvdimm/nd_e820.ko] > > undefined! > >

Re: [LKP] Re: [rcu] 44bad5b3cc: dmesg.INFO:rcu_preempt_detected_stalls_on_CPUs/tasks

On Fri, Oct 30, 2020 at 06:56:21AM -0700, Paul E. McKenney wrote: > On Fri, Oct 30, 2020 at 03:47:40PM +0800, kernel test robot wrote: > > Greeting, > > > > FYI, we noticed the following commit (built with gcc-9): > > > > commit: 44bad5b3cca2d452d17ef82841b20b42a2cf11a0 ("rcu: Do full report for

Re: [LKP] Re: [mm] e6e88712e4: stress-ng.tmpfs.ops_per_sec -69.7% regression

On Fri, Oct 30, 2020 at 02:58:35PM +, Matthew Wilcox wrote: > On Fri, Oct 30, 2020 at 10:02:45PM +0800, Chen, Rong A wrote: > > On 10/30/2020 9:17 PM, Matthew Wilcox wrote: > > > On Fri, Oct 30, 2020 at 03:17:15PM +0800, kernel test robot wrote: > > > > Details are as below: > > > >

Re: [LKP] Re: [block, scsi, ide] 3e3b42fee6: kmsg.sd#:#:#:#:[sdf]Asking_for_cache_data_failed

On Tue, Nov 17, 2020 at 08:46:46AM -0800, Bart Van Assche wrote: > On 11/17/20 8:00 AM, kernel test robot wrote: > > on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz with 32G > > memory > > > > caused below changes (please refer to attached dmesg/kmsg for entire > >

Re: [kbuild-all] Re: [PATCH] fs/nfsd: remove unused NFSDDBG_FACILITY to tame gcc

On Wed, Nov 11, 2020 at 01:35:11PM +0800, Alex Shi wrote: > I had a recall email for this patch > https://www.spinics.net/lists/linux-nfs/msg80135.html > seem your robot just omit it. :) sorry for the meaningless report, that currently the bot can't analyze the mail like this to abandon the patch

Re: arch/powerpc/mm/book3s64/pgtable.c:174:15: error: no previous prototype for 'create_section_mapping'

On Mon, Nov 23, 2020 at 07:20:46PM -0800, Dan Williams wrote: > On Mon, Nov 23, 2020 at 6:13 PM kernel test robot wrote: > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head: d5beb3140f91b1c8a3d41b14d729aefa4dcc58bc > > commit:

Re: [LKP] Re: [drm/fb] 1d46491d4a: WARNING:at_drivers/gpu/drm/drm_fb_helper.c:#drm_fb_helper_damage_work[drm_kms_helper]

On Thu, Dec 03, 2020 at 10:34:49AM +0100, Thomas Zimmermann wrote: > Hi > > Am 03.12.20 um 09:36 schrieb Oliver Sang: > > On Thu, Dec 03, 2020 at 08:41:49AM +0100, Thomas Zimmermann wrote: > > > Hi > > > > > > there should be a line in the kernel log that says something like "Damage > > >

Re: [kbuild-all] [PATCH v3 4/5] arm64: perf: Enable pmu counter direct access for perf event on armv8

On Mon, Aug 19, 2019 at 08:59:33AM +0100, Raphael Gault wrote: > Hi, > > On 8/18/19 1:37 PM, kbuild test robot wrote: > > Hi Raphael, > > > > Thank you for the patch! Yet something to improve: > > > > [auto build test ERROR on linus/master] > > [cannot apply to v5.3-rc4 next-20190816] > > [if

Re: [kbuild-all] Re: undefined reference to `start_isolate_page_range'

On Mon, Sep 07, 2020 at 03:40:08PM -0700, Randy Dunlap wrote: > Hi lkp, (or is it ktr?) > > This is sort of a shame-on-you post. As a robot, I hope that you > don't have any hard feelings about it. :) Hi Randy, thanks for the input, below warning is helpful to identify issues, we will add this

Re: [kbuild-all] Re: fs/ocfs2/suballoc.c:2430:2-8: preceding lock on line 2413

On Fri, Aug 14, 2020 at 09:52:13PM +0200, Julia Lawall wrote: > > > On Fri, 14 Aug 2020, Thomas Gleixner wrote: > > > Julia, > > > > On Fri, Aug 14 2020 at 21:00, Julia Lawall wrote: > > > On Fri, 14 Aug 2020, Thomas Gleixner wrote: > > >> That's clearly a false positive. Is there anything what

Re: [LKP] Re: [mm] 3e38e0aaca: WARNING:at_mm/memcontrol.c:#mem_cgroup_alloc

On Fri, Aug 14, 2020 at 10:00:44AM -0700, Linus Torvalds wrote: > On Fri, Aug 14, 2020 at 7:14 AM kernel test robot wrote: > > > > FYI, we noticed the following commit (built with gcc-9): > > > > commit: 3e38e0aaca9eafb12b1c4b731d1c10975cbe7974 ("mm: memcg: charge memcg > > percpu memory to the

Re: [mac80211_hwsim] 148fe295b7: hwsim.ap_long_preamble.fail

On Fri, Oct 02, 2020 at 09:38:45AM -0700, Thomas Pedersen wrote: > On 2020-10-02 01:29, kernel test robot wrote: > > Greeting, > > > > FYI, we noticed the following commit (built with gcc-9): > > > > commit: 148fe295b7d9d892b2b0f47070233ccdc70c83cd ("mac80211_hwsim: > > indicate support for

Re: [kbuild-all] Re: [PATCH] mm: memcg/slab: fix slab statistics in !SMP configuration

On Fri, Oct 02, 2020 at 10:55:06AM -0700, Roman Gushchin wrote: > On Fri, Oct 02, 2020 at 01:34:06PM +0800, Philip Li wrote: > > On Thu, Oct 01, 2020 at 05:55:59PM -0700, Roman Gushchin wrote: > > > On Fri, Oct 02, 2020 at 08:08:40AM +0800, kbuild test robot wrote

Re: [kbuild-all] aarch64-linux-gnu-ld: warning: orphan section `.eh_frame' from `drivers/tty/serial/liteuart.o' being placed in section `.eh_frame'

On Sun, Jan 31, 2021 at 11:36:33AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 6642d600b541b81931fb1ab0c041b0d68f77be7e > commit: 1da81e5562fac8286567422cc56a7fbd0dc646d4 drivers/tty/serial: add > LiteUART driver

Re: [kbuild-all] aarch64-linux-gnu-ld: warning: orphan section `.eh_frame' from `kernel/trace/trace_recursion_record.o' being placed in section `.eh_frame'

On Sun, Jan 31, 2021 at 10:09:22AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 8c947645151cc2c279c75c7f640dd8f0fc0b9aa2 > commit: 773c16705058e9be7b0f4ce124e89cd231c120a2 ftrace: Add recording of > functions that

Re: [Linux-kernel-mentees] Patches from the future - can checkpatch help?

On Tue, Feb 02, 2021 at 04:48:04AM -0800, Joe Perches wrote: > On Mon, 2021-02-01 at 22:41 +0530, Dwaipayan Ray wrote: > > The idea of a bot seems nice though in general. > > People do have all the style checking scripts at their disposal, but still > > we see style issues on the list. > > > >

Re: [kbuild-all] Re: [PATCH net-next 2/4] net: phy: dp83869: Set opmode from straps

On Tue, May 19, 2020 at 12:40:37PM -0500, Dan Murphy wrote: > kbuild > > On 5/19/20 12:19 PM, kbuild test robot wrote: > > Hi Dan, > > > > I love your patch! Perhaps something to improve: > > > > [auto build test WARNING on net-next/master] > > [also build test WARNING on robh/for-next

Re: [tip:x86/mm 1/23] arch/x86/mm/init.c:75:6: warning: no previous prototype for function 'x86_has_pat_wp'

On Tue, May 19, 2020 at 05:26:18PM -0700, Nick Desaulniers wrote: > On Tue, May 19, 2020 at 4:49 PM Li, Philip wrote: > > > > > Subject: Re: [tip:x86/mm 1/23] arch/x86/mm/init.c:75:6: warning: no > > > previous > > > prototype for function 'x86_has_pat_wp' > > > > > > Masahiro and Philip, > > >

Re: [tip:x86/mm 1/23] arch/x86/mm/init.c:75:6: warning: no previous prototype for function 'x86_has_pat_wp'

On Tue, May 19, 2020 at 06:07:14PM -0700, Nick Desaulniers wrote: > On Tue, May 19, 2020 at 5:53 PM Philip Li wrote: > > > > On Tue, May 19, 2020 at 05:26:18PM -0700, Nick Desaulniers wrote: > > > I think having in the top of the warning that this is a W=1 build will &g

Re: [kbuild-all] sh: 1: scripts/ld-version.sh: Permission denied

On Mon, Jun 01, 2020 at 01:54:29PM +0800, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162 > commit: 9553d16fa671b9621c5e2847d08bd90d3be3349c init/kconfig: Add LD_VERSION > Kconfig >

Re: 28307d938f ("percpu: make pcpu_alloc() aware of current gfp .."): BUG: kernel reboot-without-warning in boot stage

On Fri, May 29, 2020 at 01:32:28PM +0100, Filipe Manana wrote: > > > On 29/05/20 08:16, kernel test robot wrote: > > Greetings, > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master >

Re: [kbuild-all] Re: [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA

On Fri, Jun 05, 2020 at 11:57:51AM +0300, Dan Carpenter wrote: > On Fri, Jun 05, 2020 at 06:04:31AM +, Song Bao Hua (Barry Song) wrote: > > > > > > > -Original Message- > > > From: Dan Carpenter [mailto:dan.carpen...@oracle.com] > > > Sent: Thursday, June 4, 2020 11:37 PM > > > To:

Re: [kbuild-all] [PATCH] ipv6: Not to probe neighbourless routes

On Thu, Aug 29, 2019 at 04:37:42PM -0700, David Miller wrote: > > So yeah, this is one instance where the kbuild test robot's report is > making more rather than less work for us. sorry for the inconvenience caused. We monitor the lkml, and as you point out, we will continuously improve to

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Thu, Aug 29, 2019 at 06:33:53PM +0200, Borislav Petkov wrote: > On Fri, Aug 30, 2019 at 12:01:48AM +0800, kbuild test robot wrote: > > Hi tip-bot2, > > > > Thank you for the patch! Yet something to improve: > > > > [auto build test ERROR on linus/master] > > [cannot apply to v5.3-rc6

Re: [kbuild-all] [tip: timers/core] posix-cpu-timers: Use common permission check in posix_cpu_clock_get()

On Thu, Aug 29, 2019 at 01:21:59PM +0200, Thomas Gleixner wrote: > On Thu, 29 Aug 2019, kbuild test robot wrote: > > Thank you for the patch! Yet something to improve: > > > > [auto build test ERROR on linus/master] > > [cannot apply to v5.3-rc6 next-20190828] > > [if your patch is applied to the

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Fri, Aug 30, 2019 at 08:06:27AM +0200, Thomas Gleixner wrote: > Philip, > > On Fri, 30 Aug 2019, Philip Li wrote: > > > > wanna test trees, I'd suggest simply testing TIP's tip/master branch > > > which gets redone on a daily basis instead of testing p

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Fri, Aug 30, 2019 at 02:20:53PM +0800, Philip Li wrote: > On Fri, Aug 30, 2019 at 08:06:27AM +0200, Thomas Gleixner wrote: > > Philip, > > > > On Fri, 30 Aug 2019, Philip Li wrote: > > > > > > wanna test trees, I'd suggest simply testing TIP's tip/

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Fri, Aug 30, 2019 at 10:06:50AM +0200, Borislav Petkov wrote: > On Fri, Aug 30, 2019 at 02:20:53PM +0800, Philip Li wrote: > > thanks for your patience. I just realize we actually block tip-bot, but > > not tip-bot2. I will update the logic to avoid this issue, and we will &

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Fri, Aug 30, 2019 at 04:46:28PM +0200, Borislav Petkov wrote: > On Fri, Aug 30, 2019 at 10:36:45PM +0800, Philip Li wrote: > > yes, we monitor the repo pub/scm/linux/kernel/git/tip/tip.git, and will > > send build status of head > > ... and what you call "he

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Fri, Aug 30, 2019 at 11:00:02PM +0800, Philip Li wrote: > On Fri, Aug 30, 2019 at 04:46:28PM +0200, Borislav Petkov wrote: > > On Fri, Aug 30, 2019 at 10:36:45PM +0800, Philip Li wrote: > > > yes, we monitor the repo pub/scm/linux/kernel/git/tip/tip.git, and will > > >

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Fri, Aug 30, 2019 at 05:06:53PM +0200, Borislav Petkov wrote: > On Fri, Aug 30, 2019 at 11:00:02PM +0800, Philip Li wrote: > > Early on, there's requirement to blacklist a few branches, which is > > configured > > as below > > blacklist_branch: auto-.*|tmp-.*|

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Fri, Aug 30, 2019 at 09:35:57PM +0200, Borislav Petkov wrote: > On Fri, Aug 30, 2019 at 11:08:56PM +0800, Philip Li wrote: > > hi Boris, for the build status notification, we currently send to below > > address, is it still valid? If not, can you suggest one for us? > > S

Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

On Mon, Sep 02, 2019 at 11:36:51AM +0200, Borislav Petkov wrote: > On Mon, Sep 02, 2019 at 09:13:42AM +0800, Philip Li wrote: > > Thanks Boris, it is applied, and will take effect soon. > > Seems to has taken effect. I got the first build report. thanks for the info, Bori

Re: [LKP] Re: db57e98d87 ("mm/sparse.c: fix ALIGN() without power of 2 in .."): BUG: kernel reboot-without-warning in early-boot stage, last printk: early console in setup code

On Thu, Jul 16, 2020 at 03:06:13PM -0700, Andrew Morton wrote: > On Thu, 16 Jul 2020 16:32:00 +0800 kernel test robot wrote: > > > Greetings, > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > > >

Re: buildbot status?

On Sun, Jun 30, 2019 at 12:51:54PM +0300, Kalle Valo wrote: > Christoph Hellwig writes: > > > Hi buildbot maintainers, > > > > lately I usually get no, in some case a few very delayed build bot > > results for my repos. Is this as known issue? > > I have the same problem, I did receive few

[0-Day CI notification] the service will be paused during Jun 6 to Jun 11 for lab construction

Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for anyone who subscribing to the service. We will have a major lab construction during next few days, thus need to pause the service until Jun 11. Sorry for any inconvenience caused by this, we will try our best to have it

Re: [LKP] [mm/vmalloc.c] 728e0fbf26: kernel_BUG_at_mm/vmalloc.c

On Wed, Jun 05, 2019 at 09:50:20PM +0800, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-7): kindly ignore the duplicated report if you had already received one, we are working on the fix of this problem. > > commit: 728e0fbf263e3ed359c10cb13623390564102881

Re: [LKP] [mm/vmalloc.c] 728e0fbf26: kernel_BUG_at_mm/vmalloc.c

On Wed, Jun 05, 2019 at 07:54:51AM +0800, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-7): kindly ignore the duplicated report, we are working on the fix of this problem. sorry for the inconvenience. > > commit: 728e0fbf263e3ed359c10cb13623390564102881

Re: [kbuild-all] Re: drivers/scsi/ncr53c8xx.c:5306:9: sparse: sparse: cast truncates bits from constant value (58f becomes 8f)

On Fri, May 15, 2020 at 12:00:26PM -0700, Matthew Wilcox wrote: > On Sat, May 16, 2020 at 02:20:38AM +0800, kbuild test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head: 051e6b7e34b9bd24f46725f74994a4d3a653966e > > commit:

Re: [kbuild-all] ERROR: "__mulsi3" undefined!

On Tue, Jun 30, 2020 at 06:09:49AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 7c30b859a947535f2213277e827d7ac7dcff9c84 > commit: 57a10d8c1123068e3cb06434fbc9634f945d3062 ptp: Add a ptp clock driver > for IDT

Re: [kbuild-all] ERROR: "__mulsi3" undefined!

On Mon, Jun 29, 2020 at 08:04:37PM +0800, kernel test robot wrote: > Hi Sebastian, Sorry for the noise, kindly ignore this report, which is a false positive. > > First bad commit (maybe != root cause): > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master >

Re: [kbuild-all] ERROR: "__mulsi3" undefined!

On Tue, Jun 30, 2020 at 02:46:22AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68 > commit: f26e433185cb2830b933df3a4d378558fe2fccd9 arch: nios2: Enable the > common clk

Re: [kbuild-all] Re: [PATCH v1 1/4] qlge/qlge_main.c: use genric power management

On Mon, Jun 29, 2020 at 12:31:16PM -0500, Bjorn Helgaas wrote: > Vaibhav: s/genric/generic/ in the subject > > On Tue, Jun 30, 2020 at 12:09:36AM +0800, kernel test robot wrote: > > Hi Vaibhav, > > > > Thank you for the patch! Yet something to improve: > > > > [auto build test ERROR on

Re: [PATCH] mm/sparse: only sub-section aligned range would be populated

On Wed, Jul 08, 2020 at 11:20:26AM -0700, Nick Desaulniers wrote: > On Wed, Jul 8, 2020 at 12:23 AM Xia, Hui wrote: > > > > > > > > >-Original Message- > > >From: Wei Yang > > >Sent: 2020年7月1日 19:58 > > >To: lkp > > >Cc: Wei Yang ; Williams, Dan J > > >; a...@linux-foundation.org; > >

Re: [kbuild-all] ERROR: modpost: "__mulsi3" undefined!

On Sun, Jun 21, 2020 at 11:35:10AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 8b6ddd10d678bebec32381f71b6b420bafc43ad0 > commit: 30428ef5d1e8caf78639cc70a802f1cb7b1cec04 lib/test_lockup: test module > to

Re: [kbuild-all] ERROR: modpost: "__mulsi3" undefined!

On Sun, Jun 21, 2020 at 09:32:06AM +0800, kernel test robot wrote: > Hi Jonathan, Sorry Jonathan, kindly ignore this report, which is a false positive. We will fix our side problem. > > First bad commit (maybe != root cause): > > tree:

Re: [kbuild-all] ERROR: modpost: "__mulsi3" undefined!

On Sun, Jun 21, 2020 at 08:58:31AM +0800, kernel test robot wrote: > Hi Subbaraman, Sorry, kindly ignore this false positve report. We will look into it to resolve our logic issue. > > First bad commit (maybe != root cause): > > tree:

Re: [kbuild-all] ERROR: modpost: "__mulsi3" undefined!

On Sun, Jun 21, 2020 at 01:49:44PM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 8b6ddd10d678bebec32381f71b6b420bafc43ad0 > commit: d3c7b35c20d60650bac8b55c17b194adda03a979 dm: add emulated block size > target >

Re: [kbuild-all] Re: ERROR: modpost: "__mulsi3" undefined!

On Sat, Jun 20, 2020 at 09:41:28AM +0300, Denis Efremov wrote: > > > On 6/19/20 7:17 PM, kernel test robot wrote: > > Hi Denis, > > > > First bad commit (maybe != root cause): > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head:

Re: [kbuild-all] ERROR: modpost: "__mulsi3" undefined!

On Fri, Jun 19, 2020 at 07:44:00PM +0800, kernel test robot wrote: > Hi Jessica, Sorry Jessica, there's code bug that leads to multiple false positive to you. Kindly ignore these noises. > > First bad commit (maybe != root cause): > > tree:

Re: [kbuild-all] cc1: error: arch/um/include/uapi: No such file or directory

On Thu, Jun 11, 2020 at 08:39:12PM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: b29482fde649c72441d5478a4ea2c52c56d97a5e > commit: c348c16305280fe3e6c1186378f96c8634c149f9 lib: make a test module with > set/clear

Re: [LKP] Re: [gup] 17839856fd: stress-ng.vm-splice.ops_per_sec 2158.6% improvement

On Thu, Jun 11, 2020 at 01:24:09PM -0700, Linus Torvalds wrote: > On Wed, Jun 10, 2020 at 9:05 PM kernel test robot > wrote: > > > > FYI, we noticed a 2158.6% improvement of stress-ng.vm-splice.ops_per_sec > > due to commit: > > > > commit: 17839856fd588f4ab6b789f482ed3ffd7c403e1f ("gup:

[0-Day CI notification] kbuild test robot will be combined with kernel test robot

Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for subscribing to the service. It has been a long time we use both kbuild test robot and kernel test robot to send out report. From now on, we want to combine two mails to kernel test robot, which is a single voice for the

Re: [kbuild-all] [PATCH v2 1/3] kbuild: use 'include' directive to load auto.conf from top Makefile

On Sun, Jun 24, 2018 at 05:56:24PM +0900, Masahiro Yamada wrote: > Hi. > > 2018-06-24 3:59 GMT+09:00 kbuild test robot : > > Hi Masahiro, > > > > I love your patch! Yet something to improve: > > > > [auto build test ERROR on kbuild/for-next] > > [also build test ERROR on v4.18-rc1 next-20180622]

Re: [kbuild-all] arch/x86/include/asm/cmpxchg.h:245:2: error: 'asm' operand has impossible constraints

On Tue, Jan 22, 2019 at 11:08:34AM +0100, Borislav Petkov wrote: > On Tue, Jan 22, 2019 at 12:53:11PM +0800, kbuild test robot wrote: > > Hi Ingo, > > > > FYI, the error/warning still remains. > > Guys, > > we already discussed this: > >

Re: [LKP] [ide] ec7d9c9ce8: WARNING:at_fs/proc/generic.c:#remove_proc_entry

On Thu, Dec 20, 2018 at 08:05:28AM -0800, Linus Torvalds wrote: > On Thu, Dec 20, 2018 at 1:19 AM kernel test robot wrote: > > > > FYI, we noticed the following commit (built with gcc-7): > > > > commit: ec7d9c9ce897174243af4fcd201dbfc34df0f3a3 ("ide: replace ->proc_fops > > with ->proc_show") >

Re: [linus:master] BUILD REGRESSION 68abbe729567cef128b2c2141f2ed2567f3b8372

On Fri, Jun 08, 2018 at 08:48:29AM -0700, Linus Torvalds wrote: > On Fri, Jun 8, 2018 at 8:12 AM kbuild test robot wrote: > > > > arch/sh/include/asm/io.h:246:32: warning: cast to pointer from integer of > > different size [-Wint-to-pointer-cast] > > arch/x86/net/bpf_jit_comp32.c:2449 do_jit()

Re: [linus:master] BUILD REGRESSION 68abbe729567cef128b2c2141f2ed2567f3b8372

On Sat, Jun 09, 2018 at 08:29:17AM +0800, Philip Li wrote: > On Fri, Jun 08, 2018 at 08:48:29AM -0700, Linus Torvalds wrote: > > On Fri, Jun 8, 2018 at 8:12 AM kbuild test robot wrote: > > > > > > arch/sh/include/asm/io.h:246:32: warning: cast to pointer from integ

[0-Day CI notification] 0-Day CI test service will be unavailable from Sep 30 to Oct 8

Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for subscribing to the service. We will have site level power down during China national holiday, so the service will be unavailable from Asia Pacific Time Sep 30 5PM to Oct 8 5PM. We will recover it as soon as we can. Sorry

Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f

On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: > On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot > wrote: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge > >

Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'

On Mon, Feb 13, 2017 at 09:27:59AM +0530, Viresh Kumar wrote: > On 13-02-17, 11:41, Philip Li wrote: > > on the other side, this is a build issue from randconfig, looks the failure > > exists on linus/master > > head 1ce4284, and caused by 655c9df commit. Not sure whether y

Re: drivers/base/power/opp/core.c:1901:6: error: redefinition of 'dev_pm_opp_remove_table'

On Mon, Feb 13, 2017 at 10:40:53AM +, Sudeep Holla wrote: > On Sun, Feb 12, 2017 at 9:09 PM, kbuild test robot > wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head: 1ce42845f987e92eabfc6e026d44d826c25c74a5 > > commit:

Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'

On Mon, Feb 13, 2017 at 08:43:38AM +0530, Viresh Kumar wrote: > On 13-02-17, 03:35, kbuild test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head: 1ce42845f987e92eabfc6e026d44d826c25c74a5 > > commit:

Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'

On Mon, Feb 13, 2017 at 09:04:55AM +0530, Viresh Kumar wrote: > On 13-02-17, 11:35, Philip Li wrote: > > On Mon, Feb 13, 2017 at 08:43:38AM +0530, Viresh Kumar wrote: > > > On 13-02-17, 03:35, kbuild test robot wrote: > > > > tree: > > > > https

Re: [kbuild-all] [PATCH RT] usb: Use _nort in usb_hcd_pci_remove

On Tue, Apr 25, 2017 at 08:01:54AM -0400, Steven Rostedt wrote: > On Tue, 25 Apr 2017 13:26:41 +0800 > kbuild test robot wrote: > > > Hi Nate, > > > > [auto build test ERROR on usb/usb-testing] > > [also build test ERROR on v4.11-rc8 next-20170424] > > [if your patch is applied to the wrong git

  1   2   >