Hi Masahiro,
On Wed, 4 Sep 2019 15:22:09 +0900 Masahiro Yamada
wrote:
>
> For today's linux-next, please squash the following too.
>
> (This is my fault, since scripts/mkuboot.sh is a bash script)
>
>
> diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> index
Hi Masahiro,
On Wed, 4 Sep 2019 10:00:30 +0900 Masahiro Yamada
wrote:
>
> Could you fix it up as follows?
> I will squash it for tomorrow's linux-next.
>
>
> --- a/arch/powerpc/Makefile.postlink
> +++ b/arch/powerpc/Makefile.postlink
> @@ -18,7 +18,7 @@ quiet_cmd_relocs_check = CHKREL $@
>
On Wed, Sep 4, 2019 at 10:00 AM Masahiro Yamada
wrote:
>
> Hi Stephen,
>
> On Wed, Sep 4, 2019 at 9:13 AM Stephen Rothwell wrote:
> >
For today's linux-next, please squash the following too.
(This is my fault, since scripts/mkuboot.sh is a bash script)
diff --git a/scripts/Makefile.lib
Hi Stephen,
On Wed, Sep 4, 2019 at 9:13 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the kbuild tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
>
> Presumably introduced by commit
>
> 1267f9d3047d ("kbuild: add $(BASH) to run scripts with
Hi all,
After merging the kbuild tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
Presumably introduced by commit
1267f9d3047d ("kbuild: add $(BASH) to run scripts with bash-extension")
and presumably arch/powerpc/tools/unrel_branch_check.sh (which has no
#!
On Sat, Jun 2, 2018 at 10:39 PM, Arnd Bergmann wrote:
> I ran into the same thing indepently and bisected it (which led me to
> arrive at this thread).
> One additional bit of information I have is that this happens with all
> versions of
> gcc-7 for me, but not gcc-6.3 or older.
>
> Another
On Sat, Jun 2, 2018 at 10:39 PM, Arnd Bergmann wrote:
> I ran into the same thing indepently and bisected it (which led me to
> arrive at this thread).
> One additional bit of information I have is that this happens with all
> versions of
> gcc-7 for me, but not gcc-6.3 or older.
>
> Another
On Fri, Jun 1, 2018 at 6:01 AM, Kees Cook wrote:
> On Thu, May 31, 2018 at 6:56 PM, Masahiro Yamada
> wrote:
>> 2018-05-31 12:53 GMT+09:00 Kees Cook :
>>> On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
> This has been triggered by
On Fri, Jun 1, 2018 at 6:01 AM, Kees Cook wrote:
> On Thu, May 31, 2018 at 6:56 PM, Masahiro Yamada
> wrote:
>> 2018-05-31 12:53 GMT+09:00 Kees Cook :
>>> On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
> This has been triggered by
On Thu, May 31, 2018 at 6:56 PM, Masahiro Yamada
wrote:
> 2018-05-31 12:53 GMT+09:00 Kees Cook :
>> On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
>>> On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
>>> wrote:
Hi.
(+CC Kees)
2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
On Thu, May 31, 2018 at 6:56 PM, Masahiro Yamada
wrote:
> 2018-05-31 12:53 GMT+09:00 Kees Cook :
>> On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
>>> On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
>>> wrote:
Hi.
(+CC Kees)
2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
2018-05-31 12:53 GMT+09:00 Kees Cook :
> On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
>> On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
>> wrote:
>>> Hi.
>>> (+CC Kees)
>>>
>>> 2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
Hi Masahiro,
After merging the kbuild tree, today's
2018-05-31 12:53 GMT+09:00 Kees Cook :
> On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
>> On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
>> wrote:
>>> Hi.
>>> (+CC Kees)
>>>
>>> 2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
Hi Masahiro,
After merging the kbuild tree, today's
On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
> On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
> wrote:
>> Hi.
>> (+CC Kees)
>>
>> 2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
>>> Hi Masahiro,
>>>
>>> After merging the kbuild tree, today's linux-next build (x86_64
>>> allmodconfig)
On Wed, May 30, 2018 at 6:26 PM, Kees Cook wrote:
> On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
> wrote:
>> Hi.
>> (+CC Kees)
>>
>> 2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
>>> Hi Masahiro,
>>>
>>> After merging the kbuild tree, today's linux-next build (x86_64
>>> allmodconfig)
On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
wrote:
> Hi.
> (+CC Kees)
>
> 2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
>> Hi Masahiro,
>>
>> After merging the kbuild tree, today's linux-next build (x86_64
>> allmodconfig) produced these warnings:
>>
>>
On Wed, May 30, 2018 at 6:12 PM, Masahiro Yamada
wrote:
> Hi.
> (+CC Kees)
>
> 2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
>> Hi Masahiro,
>>
>> After merging the kbuild tree, today's linux-next build (x86_64
>> allmodconfig) produced these warnings:
>>
>>
Hi.
(+CC Kees)
2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
> Hi Masahiro,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
> 'wlc_phy_workarounds_nphy_rev7':
Hi.
(+CC Kees)
2018-05-31 7:40 GMT+09:00 Stephen Rothwell :
> Hi Masahiro,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
> 'wlc_phy_workarounds_nphy_rev7':
Hi Masahiro,
After merging the kbuild tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
'wlc_phy_workarounds_nphy_rev7':
drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:16563:1:
Hi Masahiro,
After merging the kbuild tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
'wlc_phy_workarounds_nphy_rev7':
drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:16563:1:
Hi all,
After merging the kbuild tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: drivers/atm/fore_200e.o(.rodata+0x2258): Section mismatch in reference
from the variable fore200e_bus to the function
.init.text:fore200e_pca_prom_read()
The variable
Hi all,
After merging the kbuild tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: drivers/atm/fore_200e.o(.rodata+0x2258): Section mismatch in reference
from the variable fore200e_bus to the function
.init.text:fore200e_pca_prom_read()
The variable
On Fri, Aug 26, 2016 at 01:58:03PM +1000, Nicholas Piggin wrote:
> On Mon, 22 Aug 2016 20:47:58 +1000
> Nicholas Piggin wrote:
>
> > On Fri, 19 Aug 2016 20:44:55 +1000
> > Nicholas Piggin wrote:
> >
> > > On Fri, 19 Aug 2016 10:37:00 +0200
> > > Michal
On Fri, Aug 26, 2016 at 01:58:03PM +1000, Nicholas Piggin wrote:
> On Mon, 22 Aug 2016 20:47:58 +1000
> Nicholas Piggin wrote:
>
> > On Fri, 19 Aug 2016 20:44:55 +1000
> > Nicholas Piggin wrote:
> >
> > > On Fri, 19 Aug 2016 10:37:00 +0200
> > > Michal Marek wrote:
> > >
> > > > On
On Mon, 22 Aug 2016 20:47:58 +1000
Nicholas Piggin wrote:
> On Fri, 19 Aug 2016 20:44:55 +1000
> Nicholas Piggin wrote:
>
> > On Fri, 19 Aug 2016 10:37:00 +0200
> > Michal Marek wrote:
> >
> > > On 2016-08-19 07:09, Stephen Rothwell
On Mon, 22 Aug 2016 20:47:58 +1000
Nicholas Piggin wrote:
> On Fri, 19 Aug 2016 20:44:55 +1000
> Nicholas Piggin wrote:
>
> > On Fri, 19 Aug 2016 10:37:00 +0200
> > Michal Marek wrote:
> >
> > > On 2016-08-19 07:09, Stephen Rothwell wrote:
>
> [snip]
>
> > > >
> > > > I may be
On Fri, 19 Aug 2016 20:44:55 +1000
Nicholas Piggin wrote:
> On Fri, 19 Aug 2016 10:37:00 +0200
> Michal Marek wrote:
>
> > On 2016-08-19 07:09, Stephen Rothwell wrote:
[snip]
> > >
> > > I may be missing something, but genksyms generates the crc's off
On Fri, 19 Aug 2016 20:44:55 +1000
Nicholas Piggin wrote:
> On Fri, 19 Aug 2016 10:37:00 +0200
> Michal Marek wrote:
>
> > On 2016-08-19 07:09, Stephen Rothwell wrote:
[snip]
> > >
> > > I may be missing something, but genksyms generates the crc's off the
> > > preprocessed C source code
On Fri, 19 Aug 2016 10:37:00 +0200
Michal Marek wrote:
> On 2016-08-19 07:09, Stephen Rothwell wrote:
> > Hi Nick,
> >
> > On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> > wrote:
> >>
> >> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin
On Fri, 19 Aug 2016 10:37:00 +0200
Michal Marek wrote:
> On 2016-08-19 07:09, Stephen Rothwell wrote:
> > Hi Nick,
> >
> > On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> > wrote:
> >>
> >> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin
> >> wrote:
> >>>
> >>> On Wed, 17 Aug
On 2016-08-19 07:09, Stephen Rothwell wrote:
> Hi Nick,
>
> On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> wrote:
>>
>> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
>>>
>>> On Wed, 17 Aug 2016 14:59:59 +0200
>>> Michal Marek
On 2016-08-19 07:09, Stephen Rothwell wrote:
> Hi Nick,
>
> On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> wrote:
>>
>> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
>>>
>>> On Wed, 17 Aug 2016 14:59:59 +0200
>>> Michal Marek wrote:
>>>
On 2016-08-17 03:44, Stephen
On Fri, 19 Aug 2016 15:09:14 +1000
Stephen Rothwell wrote:
> Hi Nick,
>
> On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> wrote:
> >
> > On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin
> > wrote:
> > >
> > > On Wed,
On Fri, 19 Aug 2016 15:09:14 +1000
Stephen Rothwell wrote:
> Hi Nick,
>
> On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> wrote:
> >
> > On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin
> > wrote:
> > >
> > > On Wed, 17 Aug 2016 14:59:59 +0200
> > > Michal Marek wrote:
> > >
Hi Nick,
On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
wrote:
>
> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
> >
> > On Wed, 17 Aug 2016 14:59:59 +0200
> > Michal Marek wrote:
> >
> > > On 2016-08-17 03:44,
Hi Nick,
On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
wrote:
>
> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
> >
> > On Wed, 17 Aug 2016 14:59:59 +0200
> > Michal Marek wrote:
> >
> > > On 2016-08-17 03:44, Stephen Rothwell wrote:
> > > >
> > > > After merging the
Hi Nick,
On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
>
> On Wed, 17 Aug 2016 14:59:59 +0200
> Michal Marek wrote:
>
> > On 2016-08-17 03:44, Stephen Rothwell wrote:
> > >
> > > After merging the kbuild tree, today's linux-next build (powerpc
Hi Nick,
On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
>
> On Wed, 17 Aug 2016 14:59:59 +0200
> Michal Marek wrote:
>
> > On 2016-08-17 03:44, Stephen Rothwell wrote:
> > >
> > > After merging the kbuild tree, today's linux-next build (powerpc
> > > ppc64_defconfig) produced
On Wed, 17 Aug 2016 14:59:59 +0200
Michal Marek wrote:
> On 2016-08-17 03:44, Stephen Rothwell wrote:
> > Hi Michal,
> >
> > After merging the kbuild tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced these warnings:
> >
> > WARNING: 25 bad relocations
> >
On Wed, 17 Aug 2016 14:59:59 +0200
Michal Marek wrote:
> On 2016-08-17 03:44, Stephen Rothwell wrote:
> > Hi Michal,
> >
> > After merging the kbuild tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced these warnings:
> >
> > WARNING: 25 bad relocations
> > c0cf2570
On 2016-08-17 03:44, Stephen Rothwell wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> WARNING: 25 bad relocations
> c0cf2570 R_PPC64_ADDR64__crc___arch_hweight16
[...]
> Introduced by commit
>
>
On 2016-08-17 03:44, Stephen Rothwell wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> WARNING: 25 bad relocations
> c0cf2570 R_PPC64_ADDR64__crc___arch_hweight16
[...]
> Introduced by commit
>
>
Hi Michal,
After merging the kbuild tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
WARNING: 25 bad relocations
c0cf2570 R_PPC64_ADDR64__crc___arch_hweight16
c0cf2578 R_PPC64_ADDR64__crc___arch_hweight32
c0cf2580 R_PPC64_ADDR64
Hi Michal,
After merging the kbuild tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
WARNING: 25 bad relocations
c0cf2570 R_PPC64_ADDR64__crc___arch_hweight16
c0cf2578 R_PPC64_ADDR64__crc___arch_hweight32
c0cf2580 R_PPC64_ADDR64
On Thu, Jun 9, 2016 at 10:37 AM, Emese Revfy wrote:
> On Thu, 9 Jun 2016 12:57:16 +0200
> Michal Marek wrote:
>
>> Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
>> > On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
>> >> Ah, yes,
On Thu, Jun 9, 2016 at 10:37 AM, Emese Revfy wrote:
> On Thu, 9 Jun 2016 12:57:16 +0200
> Michal Marek wrote:
>
>> Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
>> > On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
>> >> Ah, yes, that should default to off. We'll get a fix landed ASAP.
>>
On Thu, 9 Jun 2016 12:22:58 +1000
Stephen Rothwell wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
> Cyclomatic Complexity
On Thu, 9 Jun 2016 12:22:58 +1000
Stephen Rothwell wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
> Cyclomatic Complexity 1 kernel/bounds.c:foo
>
On Thu, 9 Jun 2016 12:57:16 +0200
Michal Marek wrote:
> Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
> > On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
> >> Ah, yes, that should default to off. We'll get a fix landed ASAP.
> >
> > Note that this
On Thu, 9 Jun 2016 12:57:16 +0200
Michal Marek wrote:
> Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
> > On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
> >> Ah, yes, that should default to off. We'll get a fix landed ASAP.
> >
> > Note that this was an allmodconfig build. The default
On Thu, 2016-06-09 at 14:05 +1000, Stephen Rothwell wrote:
> Hi Kees,
>
> On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
> >
> > Congratulations on having the gcc plugin development headers
> > successfully installed! ;)
>
> Thanks :-)
And on ppc64le too! (I think)
On Thu, 2016-06-09 at 14:05 +1000, Stephen Rothwell wrote:
> Hi Kees,
>
> On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
> >
> > Congratulations on having the gcc plugin development headers
> > successfully installed! ;)
>
> Thanks :-)
And on ppc64le too! (I think)
:)
cheers
Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
> On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
>> Ah, yes, that should default to off. We'll get a fix landed ASAP.
>
> Note that this was an allmodconfig build. The default is 'n', but
> allmodconfig will turn it on
Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
> On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
>> Ah, yes, that should default to off. We'll get a fix landed ASAP.
>
> Note that this was an allmodconfig build. The default is 'n', but
> allmodconfig will turn it on (as will allyesconfig).
Hi Kees,
On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
>
> Congratulations on having the gcc plugin development headers
> successfully installed! ;)
Thanks :-)
> Ah, yes, that should default to off. We'll get a fix landed ASAP.
Note that this was an allmodconfig
Hi Kees,
On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
>
> Congratulations on having the gcc plugin development headers
> successfully installed! ;)
Thanks :-)
> Ah, yes, that should default to off. We'll get a fix landed ASAP.
Note that this was an allmodconfig build. The default is
On Wed, Jun 8, 2016 at 7:22 PM, Stephen Rothwell wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
> Cyclomatic Complexity 1
On Wed, Jun 8, 2016 at 7:22 PM, Stephen Rothwell wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
> Cyclomatic Complexity 1 kernel/bounds.c:foo
>
Hi Michal,
After merging the kbuild tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
Cyclomatic Complexity 1 kernel/bounds.c:foo
Cyclomatic Complexity 1 arch/x86/kernel/asm-offsets_64.c:main
Cyclomatic
Hi Michal,
After merging the kbuild tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
Cyclomatic Complexity 1 kernel/bounds.c:foo
Cyclomatic Complexity 1 arch/x86/kernel/asm-offsets_64.c:main
Cyclomatic
61 matches
Mail list logo