On Tue, Apr 06, 2021 at 05:28:36PM +, Gustavo Pimentel wrote:
> On Tue, Apr 6, 2021 at 15:15:40, Greg KH wrote:
>
> > On Tue, Apr 06, 2021 at 02:13:53PM +, Gustavo Pimentel wrote:
> > > On Tue, Apr 6, 2021 at 15:7:23, Greg KH wrote:
> > >
> > > > On Tue, Apr 06, 2021 at 09:44:41PM
On Tue, Apr 6, 2021 at 15:15:40, Greg KH wrote:
> On Tue, Apr 06, 2021 at 02:13:53PM +, Gustavo Pimentel wrote:
> > On Tue, Apr 6, 2021 at 15:7:23, Greg KH wrote:
> >
> > > On Tue, Apr 06, 2021 at 09:44:41PM +1000, Stephen Rothwell wrote:
> > > > Hi all,
> > > >
> > > > After merging the
On Tue, Apr 06, 2021 at 02:13:53PM +, Gustavo Pimentel wrote:
> On Tue, Apr 6, 2021 at 15:7:23, Greg KH wrote:
>
> > On Tue, Apr 06, 2021 at 09:44:41PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > After merging the char-misc tree, today's linux-next build (htmldocs)
> > >
On Tue, Apr 6, 2021 at 15:7:23, Greg KH wrote:
> On Tue, Apr 06, 2021 at 09:44:41PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the char-misc tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/misc-devices/dw-xdata-pcie.rst:20:
On Tue, Apr 06, 2021 at 09:44:41PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/misc-devices/dw-xdata-pcie.rst:20: WARNING: Unexpected
> indentation.
>
Hi all,
On Tue, 6 Apr 2021 21:44:41 +1000 Stephen Rothwell
wrote:
>
> After merging the char-misc tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/misc-devices/dw-xdata-pcie.rst:20: WARNING: Unexpected
> indentation.
>
a
> ; Jolly Shah
> Cc: Arnd Bergmann ; Linux Next Mailing List n...@vger.kernel.org>; Linux Kernel Mailing List ker...@vger.kernel.org>
> Subject: Re: linux-next: build warning after merge of the char-misc tree
>
> CAUTION: This message has originated from an External Source. Pl
On Fri, May 01, 2020 at 04:28:06PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/crypto/xilinx/zynqmp-aes-gcm.c: In function 'zynqmp_handle_aes_req':
>
On Fri, Apr 26, 2019 at 7:30 AM Patrick Venture wrote:
>
> On Thu, Apr 25, 2019 at 11:25 PM Greg KH wrote:
> >
> > On Fri, Apr 26, 2019 at 03:56:53PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > After merging the char-misc tree, today's linux-next build (x86_64
> > > allmodconfig)
On Thu, Apr 25, 2019 at 11:25 PM Greg KH wrote:
>
> On Fri, Apr 26, 2019 at 03:56:53PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the char-misc tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/misc/aspeed-p2a-ctrl.c: In function
On Fri, Apr 26, 2019 at 03:56:53PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/misc/aspeed-p2a-ctrl.c: In function 'aspeed_p2a_mmap':
> drivers/misc/aspeed-p2a-ctrl.c:110:2:
wt., 2 paź 2018 o 11:56 Srinivas Kandagatla
napisał(a):
>
>
>
> On 02/10/18 10:49, Bartosz Golaszewski wrote:
> > this looks like a false positive - this routine is used in
> > ./drivers/nvmem/core.c at line 943 in this revision.
> >
> Note that the caller is under
> #if IS_ENABLED(CONFIG_OF)
>
wt., 2 paź 2018 o 11:56 Srinivas Kandagatla
napisał(a):
>
>
>
> On 02/10/18 10:49, Bartosz Golaszewski wrote:
> > this looks like a false positive - this routine is used in
> > ./drivers/nvmem/core.c at line 943 in this revision.
> >
> Note that the caller is under
> #if IS_ENABLED(CONFIG_OF)
>
On 02/10/18 10:49, Bartosz Golaszewski wrote:
this looks like a false positive - this routine is used in
./drivers/nvmem/core.c at line 943 in this revision.
Note that the caller is under
#if IS_ENABLED(CONFIG_OF)
so this warning!
--srini
Best regards,
On 02/10/18 10:49, Bartosz Golaszewski wrote:
this looks like a false positive - this routine is used in
./drivers/nvmem/core.c at line 943 in this revision.
Note that the caller is under
#if IS_ENABLED(CONFIG_OF)
so this warning!
--srini
Best regards,
wt., 2 paź 2018 o 11:12 Stephen Rothwell napisał(a):
>
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (i386
> defconfig) produced this warning:
>
> drivers/nvmem/core.c:496:1: warning: 'nvmem_find_cell_by_index' defined but
> not used [-Wunused-function]
>
wt., 2 paź 2018 o 11:12 Stephen Rothwell napisał(a):
>
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (i386
> defconfig) produced this warning:
>
> drivers/nvmem/core.c:496:1: warning: 'nvmem_find_cell_by_index' defined but
> not used [-Wunused-function]
>
wt., 2 paź 2018 o 07:31 Stephen Rothwell napisał(a):
>
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/nvmem/lpc18xx_eeprom.c: In function 'lpc18xx_eeprom_remove':
> drivers/nvmem/lpc18xx_eeprom.c:258:6: warning:
wt., 2 paź 2018 o 07:31 Stephen Rothwell napisał(a):
>
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/nvmem/lpc18xx_eeprom.c: In function 'lpc18xx_eeprom_remove':
> drivers/nvmem/lpc18xx_eeprom.c:258:6: warning:
On Tue, Dec 12, 2017 at 02:39:10PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, today's linux-next build
> (x86_64_allmodconfig) produced this warning:
>
> drivers/misc/mic/vop/vop_vringh.c: In function 'vop_ioctl':
> drivers/misc/mic/vop/vop_vringh.c:1001:1:
On Tue, Dec 12, 2017 at 02:39:10PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, today's linux-next build
> (x86_64_allmodconfig) produced this warning:
>
> drivers/misc/mic/vop/vop_vringh.c: In function 'vop_ioctl':
> drivers/misc/mic/vop/vop_vringh.c:1001:1:
g List ker...@vger.kernel.org>; Vitaly Kuznetsov <vkuzn...@redhat.com>; KY
> Srinivasan <k...@microsoft.com>; Andy Shevchenko
> <andy.shevche...@gmail.com>
> Subject: Re: linux-next: build warning after merge of the char-misc tree
>
> On Thu, Jul 20, 2017 at 0
sov ; KY
> Srinivasan ; Andy Shevchenko
>
> Subject: Re: linux-next: build warning after merge of the char-misc tree
>
> On Thu, Jul 20, 2017 at 02:12:03PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the char-misc tree, yesterday's linux
On Thu, Jul 20, 2017 at 02:12:03PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, yesterday's linux-next build (i386
> defconfig) produced this warning:
>
> In file included from /home/sfr/next/next/arch/x86/entry/vdso/vma.c:25:0:
>
On Thu, Jul 20, 2017 at 02:12:03PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, yesterday's linux-next build (i386
> defconfig) produced this warning:
>
> In file included from /home/sfr/next/next/arch/x86/entry/vdso/vma.c:25:0:
>
On Thu, Jul 20, 2017 at 02:12:03PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, yesterday's linux-next build (i386
> defconfig) produced this warning:
>
> In file included from /home/sfr/next/next/arch/x86/entry/vdso/vma.c:25:0:
>
On Thu, Jul 20, 2017 at 02:12:03PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, yesterday's linux-next build (i386
> defconfig) produced this warning:
>
> In file included from /home/sfr/next/next/arch/x86/entry/vdso/vma.c:25:0:
>
Hi Stephen,
2017-03-28 12:31 GMT+09:00 Stephen Rothwell :
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> ./usr/include/linux/aspeed-lpc-ctrl.h:44: found __[us]{8,16,32,64} type
> without #include
Hi Stephen,
2017-03-28 12:31 GMT+09:00 Stephen Rothwell :
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> ./usr/include/linux/aspeed-lpc-ctrl.h:44: found __[us]{8,16,32,64} type
> without #include
>
> Introduced by
On Tue, Mar 31, 2015 at 09:35:45PM +0200, Fabian Frederick wrote:
>
>
> > On 27 March 2015 at 08:48 Stephen Rothwell wrote:
> >
> >
> > Hi all,
> >
> > After merging the char-misc tree, today's linux-next build (powerpc
> > allyesconfig) produced this warning:
> >
> > In file included from
On Tue, Mar 31, 2015 at 09:35:45PM +0200, Fabian Frederick wrote:
On 27 March 2015 at 08:48 Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the char-misc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
In file included from
> On 27 March 2015 at 08:48 Stephen Rothwell wrote:
>
>
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
>
> In file included from include/linux/module.h:17:0,
> from drivers/uio/uio_pdrv_genirq.c:21:
>
On 27 March 2015 at 08:48 Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the char-misc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
In file included from include/linux/module.h:17:0,
from
On Fri, Mar 1, 2013 at 6:16 PM, Arnd Bergmann wrote:
> On Friday 01 March 2013, Sedat Dilek wrote:
>> I have seen a lot of such failures when using the Freetz (a small
>> router project) build-system with gcc-4.7-x where "-Os" is default
>> optimization-level.
>>
>> Last, when I tried to
On Friday 01 March 2013, Sedat Dilek wrote:
> I have seen a lot of such failures when using the Freetz (a small
> router project) build-system with gcc-4.7-x where "-Os" is default
> optimization-level.
>
> Last, when I tried to integrate ltrace GIT snapshots into Freetz.
> All these
On Fri, Feb 15, 2013 at 9:05 PM, Arnd Bergmann wrote:
> On Friday 15 February 2013, Greg KH wrote:
>> On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
>> >
>> > After merging the char-misc tree, today's linux-next build (x86_64
>> > allmodconfig) produced this warning:
>> >
>> >
On Fri, Feb 15, 2013 at 9:05 PM, Arnd Bergmann a...@arndb.de wrote:
On Friday 15 February 2013, Greg KH wrote:
On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
On Friday 01 March 2013, Sedat Dilek wrote:
I have seen a lot of such failures when using the Freetz (a small
router project) build-system with gcc-4.7-x where -Os is default
optimization-level.
Last, when I tried to integrate ltrace GIT snapshots into Freetz.
All these build-errors could
On Fri, Mar 1, 2013 at 6:16 PM, Arnd Bergmann a...@arndb.de wrote:
On Friday 01 March 2013, Sedat Dilek wrote:
I have seen a lot of such failures when using the Freetz (a small
router project) build-system with gcc-4.7-x where -Os is default
optimization-level.
Last, when I tried to
On Friday 15 February 2013, Greg KH wrote:
> On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
> >
> > After merging the char-misc tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/w1/slaves/w1_therm.c: In function 'w1_therm_read':
>
On Friday 15 February 2013, Greg KH wrote:
> On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the char-misc tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/w1/slaves/w1_therm.c: In function
On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/w1/slaves/w1_therm.c: In function 'w1_therm_read':
> drivers/w1/slaves/w1_therm.c:245:15: warning:
On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
Hi all,
After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/w1/slaves/w1_therm.c: In function 'w1_therm_read':
drivers/w1/slaves/w1_therm.c:245:15: warning: 'crc'
On Friday 15 February 2013, Greg KH wrote:
On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
Hi all,
After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/w1/slaves/w1_therm.c: In function 'w1_therm_read':
On Friday 15 February 2013, Greg KH wrote:
On Fri, Feb 15, 2013 at 04:26:57PM +1100, Stephen Rothwell wrote:
After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/w1/slaves/w1_therm.c: In function 'w1_therm_read':
45 matches
Mail list logo