On Tue, Mar 23, 2021 at 04:51:45PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Building Linus' tree, today's linux-next build (x86_64 allnoconfig)
> produced this warning:
>
> kernel/static_call.c: In function '__static_call_update':
> kernel/static_call.c:153:18: warning: unused variable 'mod'
> Hi all,
>
> On Thu, 18 Feb 2021 22:47:57 + "Ernst, Justin"
> wrote:
> >
> > Hi,
> > We made a special effort to squash the unexpected indentation warnings in
> > c159376490ee
> (https://lore.kernel.org/lkml/20201130214304.369348-1-justin.er...@hpe.com/),
> so I was surprised to
> see thi
Hi all,
On Thu, 18 Feb 2021 22:47:57 + "Ernst, Justin" wrote:
>
> Hi,
> We made a special effort to squash the unexpected indentation warnings in
> c159376490ee
> (https://lore.kernel.org/lkml/20201130214304.369348-1-justin.er...@hpe.com/),
> so I was surprised to see this again.
> Commit:
Hi,
We made a special effort to squash the unexpected indentation warnings in
c159376490ee
(https://lore.kernel.org/lkml/20201130214304.369348-1-justin.er...@hpe.com/),
so I was surprised to see this again.
Commit:
c9624cb7db1c ("x86/platform/uv: Update sysfs documentation")
is the cul
On Tue, Oct 27, 2020 at 8:28 PM Stephen Rothwell wrote:
>
> Hi all,
>
> In Linus' tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/admin-guide/LSM/SafeSetID.rst:110: WARNING: Title underline too
> short.
Thanks for the heads up. I think someone sent a patch to
Hi Micah,
On Wed, 28 Oct 2020 08:56:00 -0700 Micah Morton wrote:
>
> Thanks for the heads up. I think someone sent a patch to fix this
> yesterday: https://marc.info/?l=linux-doc&m=160379233902729&w=2
>
> Do I need to do anything else or should that cover it?
That should be fine, thanks.
--
C
Em Fri, 2 Nov 2018 07:30:16 -0300
Mauro Carvalho Chehab escreveu:
> Hi Stephen,
>
> Em Thu, 1 Nov 2018 08:28:20 +1100
> Stephen Rothwell escreveu:
>
> > Hi all,
> >
> > Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> >
> > ./usr/include/linux
Hi Stephen,
Em Thu, 1 Nov 2018 08:28:20 +1100
Stephen Rothwell escreveu:
> Hi all,
>
> Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> ./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64} type
> without #include
>
> Introduced
Em Thu, 1 Nov 2018 08:28:20 +1100
Stephen Rothwell escreveu:
> Hi all,
>
> Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> ./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64} type
> without #include
>
> Introduced by commit
>
Hi Ingo,
On Thu, 2 Nov 2017 22:08:19 +0100 Ingo Molnar wrote:
>
> The warnings are harmless, I'll take care of them tomorrow.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
* Stephen Rothwell wrote:
> Hi Linus,
>
> Just building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> warning: objtool: x86 instruction decoder differs from kernel
>
> This is a change since yesterday. Linus' tree has been updated with
> these commi
On 10/30/2016 12:29 AM, Geert Uytterhoeven wrote:
> Hi Linus,
>
> On Fri, Oct 28, 2016 at 1:01 AM, Linus Torvalds
> wrote:
>> On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
>> wrote:
>>>
>>> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
>>> does seem to disable a lot of
Hi Linus,
On Fri, Oct 28, 2016 at 1:01 AM, Linus Torvalds
wrote:
> On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
> wrote:
>>
>> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
>> does seem to disable a lot of build-time testing.
>
> Actually, we should probably just make t
Hi Linus,
On Thu, 27 Oct 2016 16:01:22 -0700 Linus Torvalds
wrote:
>
> In the meantime, thanks for noticing and letting me know.
It was pointed out by the extra checking you asked me to add in order
to easier detect new warnings for code added to linux-next :-)
--
Cheers,
Stephen Rothwell
On Thu, Oct 27, 2016 at 4:05 PM, Alexander Potapenko wrote:
>
> Maybe we could just reverse the MEMORY_HOTPLUG->!KASAN dependency to
> make it KASAN->!MEMORY_HOTPLUG?
Yes, that was my initial approach too, but then I decided that I'd
rather build-test both together anyway. Since I can. So that ju
On Thu, Oct 27, 2016 at 4:01 PM, Linus Torvalds
wrote:
> On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
> wrote:
>>
>> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
>> does seem to disable a lot of build-time testing.
>
> Actually, we should probably just make the MEMORY_H
On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
wrote:
>
> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
> does seem to disable a lot of build-time testing.
Actually, we should probably just make the MEMORY_HOTPLUG dependency be
depends on COMPILE_TEST || !KASAN
s
On Thu, Oct 27, 2016 at 3:29 PM, Stephen Rothwell wrote:
>
> Building your tree, today's linux-next build (powerpc ppc64_defconfig)
> produced this warning:
>
> mm/memory_hotplug.c: In function 'try_offline_node':
> mm/memory_hotplug.c:2120:6: warning: unused variable 'i' [-Wunused-variable]
> in
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Stephen Rothwell
> Sent: Tuesday, December 17, 2013 2:52 PM
> To: David Miller; net...@vger.kernel.org
> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Fastabend,
On 10/28/2012 09:44 PM, Mauro Carvalho Chehab wrote:
Em Wed, 24 Oct 2012 13:43:33 +1100
Stephen Rothwell escreveu:
Hi Mauro,
After merging the origin tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/media/usb/dvb-usb-v2/dvb_usb_core.c: In function 'dvb_usb_
Em Wed, 24 Oct 2012 13:43:33 +1100
Stephen Rothwell escreveu:
> Hi Mauro,
>
> After merging the origin tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/media/usb/dvb-usb-v2/dvb_usb_core.c: In function 'dvb_usb_ctrl_feed':
> drivers/media/usb/dvb-usb-v2/d
21 matches
Mail list logo
