RE: [kbuild-all] Re: [PATCH] wfx: fix irqf_oneshot.cocci warnings

2021-03-16 Thread Li, Philip
> Subject: [kbuild-all] Re: [PATCH] wfx: fix irqf_oneshot.cocci warnings > > Hello, > > On Monday 15 March 2021 22:09:20 CET kernel test robot wrote: > > > > From: kernel test robot > > > > drivers/net/wireless/silabs/wfx/bus_sdio.c:134:8-33: ERROR: Threaded IRQ > > with no primary handler requ

RE: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC with prefixes of arbitrary length in PIO

2020-11-12 Thread Li, Philip
> > On Fri, 13 Nov 2020 00:32:55 +0000 Li, Philip wrote: > > > Subject: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC > with > > > prefixes of arbitrary length in PIO > > > > > > On Wed, 11 Nov 2020 09:34:24 +0800 kernel test robot wr

RE: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC with prefixes of arbitrary length in PIO

2020-11-12 Thread Li, Philip
> Subject: [kbuild-all] Re: [PATCH net-next] net: Variable SLAAC: SLAAC with > prefixes of arbitrary length in PIO > > On Wed, 11 Nov 2020 09:34:24 +0800 kernel test robot wrote: > > If you fix the issue, kindly add following tag as appropriate > > Reported-by: kernel test robot > > Good people

[0-Day CI notification] the service will be paused from 11/6/2020 5 PM to 11/9/2020 10 AM (PRC time)

2020-11-05 Thread Li, Philip
Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for anyone who subscribes to the service. We will have a lab power construction this weekend, thus need to pause the service for about 3 days, at PRC time from 11/6/2020 5 PM to 11/9/2020 10 AM. Sorry for any inconvenience caus

RE: [kbuild-all] Re: ld.lld: warning: fs/built-in.a(afs/cell.o):(.data..L__unnamed_8) is being placed in '.data..L__unnamed_8'

2020-10-24 Thread Li, Philip
> Subject: [kbuild-all] Re: ld.lld: warning: fs/built- > in.a(afs/cell.o):(.data..L__unnamed_8) is being placed in > '.data..L__unnamed_8' > > https://github.com/ClangBuiltLinux/linux/issues/1185 sorry for false positive, we will ignore all lld warning related to "being placed in", the initial ig

RE: [kbuild-all] Re: [PATCH v4 4/7] iommu/vt-d: Handle non-page aligned address

2020-07-08 Thread Li, Philip
> Subject: [kbuild-all] Re: [PATCH v4 4/7] iommu/vt-d: Handle non-page aligned > address > > Hi Jacob, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on iommu/next] > [also build test WARNING on linux/master linus/master v5.8-rc4 next-20200707] > [If your

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

2020-05-19 Thread Li, Philip
> 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, > We're seeing a bunch of -Wmissing-prototypes warnings from 0day bot > suddenly today. Did something change on the Kbuild or 0day bot side? Hi Nick, W

RE: [kbuild-all] drivers/usb/cdns3/drd.c:332:17: sparse: sparse: too many warnings

2020-05-18 Thread Li, Philip
> Subject: [kbuild-all] drivers/usb/cdns3/drd.c:332:17: sparse: sparse: too many > warnings > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: b9bbe6ed63b2b9f2c9ee5cbd0f2c946a2723f4ce > commit: 70d8b9e5e63d212019ba3f6823c8ec3d2df87645 usb: cdns3: mak

RE: [RT PATCH v2] net/xfrm/xfrm_ipcomp: Protect scratch buffer with local_lock

2019-08-20 Thread Li, Philip
> Subject: Re: [RT PATCH v2] net/xfrm/xfrm_ipcomp: Protect scratch buffer with > local_lock > > Hi, > > On 20/08/19 13:35, kbuild test robot wrote: > > Hi Juri, > > > > Thank you for the patch! Yet something to improve: > > > > [auto build test ERROR on linus/master] > > [cannot apply to v5.3-rc5

RE: [kbuild-all] [PATCH] regulator: lp87565: Convert to use regulator_set/get_current_limit_regmap

2019-03-01 Thread Li, Philip
> Subject: Re: [kbuild-all] [PATCH] regulator: lp87565: Convert to use > regulator_set/get_current_limit_regmap > > kbuild test robot 於 2019年3月1日 週五 下午7:32寫道: > > > > Hi Axel, > > > > Thank you for the patch! Yet something to improve: > > > > [auto build test ERROR on regulator/for-next] > > [als

RE: [kbuild-all] make[3]: *** No rule to make target 'arch/mips/boot/dts/brcm/bcm93384wvg.dtb', needed by '__build'.

2018-11-02 Thread Li, Philip
> Subject: Re: [kbuild-all] make[3]: *** No rule to make target > 'arch/mips/boot/dts/brcm/bcm93384wvg.dtb', needed by '__build'. > > On Wed, Oct 31, 2018 at 9:18 PM kbuild test robot wrote: > > > > Hi Rob, > > > > FYI, the error/warning still remains. > > I replied on another one of these repor

RE: [kbuild-all] [PATCH RT 2/2] watchdog, rt: prevent deferral of watchdogd wakeup

2018-09-29 Thread Li, Philip
> Subject: Re: [kbuild-all] [PATCH RT 2/2] watchdog, rt: prevent deferral of > watchdogd wakeup > > On 2018-09-29 08:38:55 [+0200], Thomas Gleixner wrote: > > On Sat, 29 Sep 2018, kbuild test robot wrote: > > > [also build test ERROR on v4.19-rc5 next-20180928] > > > [if your patch is applied to t

RE: [kbuild-all] include/linux/syscalls.h:211:18: error: 'sys_sparc_remap_file_pages' alias between functions of incompatible types 'long int(long unsigned int, long unsigned int, long unsigned int, l

2018-05-29 Thread Li, Philip
> > Hi Al, > > FYI, the error/warning still remains. hi AI, kindly ignore this, the warning below may be caused by gcc-8.1 upgrade. we will double check to reduce noises. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 0044cdeb731313f20b63cb564

RE: cross-compiling a 64-bit kernel on a 32-bit host

2018-05-10 Thread Li, Philip
> Subject: Re: cross-compiling a 64-bit kernel on a 32-bit host > > Hi Josh, > > CC LKP team. > > On Thu, May 10, 2018 at 05:36:19PM -0500, Josh Poimboeuf wrote: > >Hi Fengguang, > > > >I occasionally get compilation bug reports from people who are > >cross-compiling an x86-64 kernel target on

RE: Makefile:636: arch/score/Makefile: No such file or directory

2018-04-26 Thread Li, Philip
> >Please stop trying to build the removed architectures: tile, blackfin, > >metag, m32r, frv, mn10300, cris and score. > > > >https://lwn.net/Articles/748074/ has details about why this broke. > > Sorry about that! It looks the architectures removal is not thorough > enough. Hao, would you help

RE: [kbuild-all] [PATCH] drm: fix drm-get-put.cocci warnings

2018-04-16 Thread Li, Philip
> Subject: Re: [kbuild-all] [PATCH] drm: fix drm-get-put.cocci warnings > > On Thu, Apr 12, 2018 at 07:54:10AM +0200, Julia Lawall wrote: > > From: Fengguang Wu > > > > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and > > drm_*_unreference() helpers. > > > > Generated by

RE: [PATCH 05/45] C++: Set compilation as C++ for .c files

2018-04-10 Thread Li, Philip
> > Hi David, > > On Tue, Apr 10, 2018 at 09:44:14AM +0100, David Howells wrote: > >Hi Fengguang, > > > >There's another kbuild test that's probably worth adding if you don't do it > >already: create a c++ source file that just #includes all the exported UAPI > >headers and then try to build it.

RE: [GIT PULL 2/3] ARM: SoC driver updates for 4.15

2017-11-17 Thread Li, Philip
On Fri, Nov 17, 2017 at 7:50 AM, Fengguang Wu wrote: > On Fri, Nov 17, 2017 at 12:25:12AM +0100, Arnd Bergmann wrote: > >On Thu, Nov 16, 2017 at 11:29 PM, Linus Torvalds > > wrote: > >> On Thu, Nov 16, 2017 at 2:02 PM, Arnd Bergmann wrote: > >>> > >>> ARM: SoC driver updates for v4.15 > >> > >> No

RE: parisc:generic-64bit_defconfig build failures due to 'kbuild: handle libs-y archives separately...'

2017-07-18 Thread Li, Philip
> > On Wed, Jul 19, 2017 at 12:01:06PM +1000, Nicholas Piggin wrote: > >On Tue, 18 Jul 2017 23:58:07 +0200 > >Helge Deller wrote: > > > >> > >> This outstanding patch will fix it: > >> https://patchwork.kernel.org/patch/9832033/ > >> Helge > >> Von meinem Samsung Gerät gesendet. > > > >Thanks for

RE: [kbuild-all] Makefile:541: arch/avr32/Makefile: No such file or directory

2017-05-14 Thread Li, Philip
> Hi robby, > > Too much automation maybe?? > > See the commit message: > avr32: remove support for AVR32 > and then the error message... > Thanks for input, we had applied patch to remove arv testing, which will fully take effect this week, sorry for some noises. > > On 05/13/17 17:05,

RE: [PATCH v2 08/17] libnvdimm: introduce nvdimm_flush() and nvdimm_has_flush()

2016-07-10 Thread Li, Philip
> -Original Message- > From: Williams, Dan J > Sent: Sunday, July 10, 2016 1:01 PM > To: lkp > Cc: kbuild-...@01.org; linux-nvd...@lists.01.org; linux-fsdevel fsde...@vger.kernel.org>; Linux ACPI ; Ross > Zwisler ; Christoph Hellwig ; > linux- > ker...@vger.kernel.org > Subject: Re: [P

RE: drivers/base/power/opp/cpu.c:120:5: error: redefinition of 'dev_pm_opp_set_sharing_cpus'

2016-04-05 Thread Li, Philip
> -Original Message- > From: Viresh Kumar [mailto:viresh.ku...@linaro.org] > Sent: Tuesday, April 5, 2016 11:10 AM > To: Wu, Fengguang > Cc: kbuild-...@01.org; linux-kernel@vger.kernel.org; Rafael J. Wysocki > ; Stephen Boyd > Subject: Re: drivers/base/power/opp/cpu.c:120:5: error: rede

RE: gcm.c:undefined reference to `crypto_aead_setauthsize'

2016-04-05 Thread Li, Philip
> -Original Message- > From: Herbert Xu [mailto:herb...@gondor.apana.org.au] > Sent: Monday, April 4, 2016 10:00 PM > To: Wu, Fengguang > Cc: Sabrina Dubroca ; kbuild-...@01.org; > linux-kernel@vger.kernel.org; Hannes Frederic Sowa > ; Linux Crypto Mailing List > > Subject: Re: gcm.c:un

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

2016-03-19 Thread Li, Philip
> -Original Message- > From: Krzysztof Kozlowski [mailto:k.kozlow...@samsung.com] > Sent: Friday, March 18, 2016 11:22 AM > To: Li, Philip > Cc: Wu, Fengguang ; Al Viro > ; kbuild-...@01.org; linux-kernel@vger.kernel.org; > Richard Weinberger > Subject: Re: arch

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

2016-03-18 Thread Li, Philip
> -Original Message- > From: Richard Weinberger [mailto:rich...@nod.at] > Sent: Friday, March 18, 2016 4:59 PM > To: Li, Philip ; Krzysztof Kozlowski > > Cc: Wu, Fengguang ; Al Viro > ; kbuild-...@01.org; linux-kernel@vger.kernel.org > Subject: Re: arch/x86/um/us