Re: linux-next: Tree for Oct 23
On 10/22/19 11:05 PM, Shaokun Zhang wrote:
+Cc: Mark Salyzyn
There is a compiler failure on arm64 platform, as follow:
zhangshaokun@ubuntu:~/linux-next$ make -j64
CALLscripts/atomic/check-atomics.sh
CC arch/arm64/kernel/asm-offsets.s
In file included from ./include/linux/sysctl.h:30:0,
from ./include/linux/umh.h:9,
from ./include/linux/kmod.h:9,
from ./include/linux/module.h:13,
from ./include/linux/acpi.h:29,
from ./include/acpi/apei.h:9,
from ./include/acpi/ghes.h:5,
from ./include/linux/arm_sdei.h:8,
from arch/arm64/kernel/asm-offsets.c:10:
./include/uapi/linux/sysctl.h:561:29: error: expected ‘,’ or ‘}’ before
‘__attribute__’
NET_IPV6_TEMP_PREFERED_LFT __attribute__((deprecated)) = /* NOTYPO */
^
scripts/Makefile.build:99: recipe for target 'arch/arm64/kernel/asm-offsets.s'
failed
make[1]: *** [arch/arm64/kernel/asm-offsets.s] Error 1
Makefile:1108: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
It's the commit <79f0cf35dccb> ("treewide: cleanup: replace prefered with
preferred").
Ack, will split up patch and resubmit, compiler differences make that
part of the cleanup unworkable.
Thanks,
Shaokun
On 2019/10/23 12:55, Stephen Rothwell wrote:
Hi all,
Changes since 20191022:
Non-merge commits (relative to Linus' tree): 5530
5340 files changed, 192671 insertions(+), 90844 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log
files in the Next directory. Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).
Below is a summary of the state of the merge.
I am currently merging 310 trees (counting Linus' and 78 trees of bug
fix patches pending for the current merge release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
Gortmaker for triage and bug fixes.
Re: linux-next: Tree for Oct 23
Hi Geert,
On 2019/10/23 14:44, Geert Uytterhoeven wrote:
> On Wed, Oct 23, 2019 at 8:17 AM Shaokun Zhang
> wrote:
>> +Cc: Mark Salyzyn
>>
>> There is a compiler failure on arm64 platform, as follow:
>> zhangshaokun@ubuntu:~/linux-next$ make -j64
>> CALLscripts/atomic/check-atomics.sh
>> CC arch/arm64/kernel/asm-offsets.s
>> In file included from ./include/linux/sysctl.h:30:0,
>> from ./include/linux/umh.h:9,
>> from ./include/linux/kmod.h:9,
>> from ./include/linux/module.h:13,
>> from ./include/linux/acpi.h:29,
>> from ./include/acpi/apei.h:9,
>> from ./include/acpi/ghes.h:5,
>> from ./include/linux/arm_sdei.h:8,
>> from arch/arm64/kernel/asm-offsets.c:10:
>> ./include/uapi/linux/sysctl.h:561:29: error: expected ‘,’ or ‘}’ before
>> ‘__attribute__’
>> NET_IPV6_TEMP_PREFERED_LFT __attribute__((deprecated)) = /* NOTYPO */
>> ^
>> scripts/Makefile.build:99: recipe for target
>> 'arch/arm64/kernel/asm-offsets.s' failed
>> make[1]: *** [arch/arm64/kernel/asm-offsets.s] Error 1
>> Makefile:1108: recipe for target 'prepare0' failed
>> make: *** [prepare0] Error 2
>>
>> It's the commit <79f0cf35dccb> ("treewide: cleanup: replace prefered with
>> preferred").
>
> After receiving a report from kisskb for failures for m68k, looking at
> http://kisskb.ellerman.id.au/kisskb/head/f3c452cfc59c817950b150b51ec2b33409d7640b/
> and doing some testing, it looks like this construct is supported by gcc-7
> and gcc-8, but not by gcc-4.6.3 and gcc-5. Don't know about gcc-6.
>
GCC version is 5.4.0
zhangshaokun@ubuntu:~/linux-next$ gcc --version
gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Thanks,
> Gr{oetje,eeting}s,
>
> Geert
>
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> ge...@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
>
> .
>
Re: linux-next: Tree for Oct 23
On 10/22/19 11:44 PM, Geert Uytterhoeven wrote:
> On Wed, Oct 23, 2019 at 8:17 AM Shaokun Zhang
> wrote:
>> +Cc: Mark Salyzyn
>>
>> There is a compiler failure on arm64 platform, as follow:
>> zhangshaokun@ubuntu:~/linux-next$ make -j64
>> CALLscripts/atomic/check-atomics.sh
>> CC arch/arm64/kernel/asm-offsets.s
>> In file included from ./include/linux/sysctl.h:30:0,
>> from ./include/linux/umh.h:9,
>> from ./include/linux/kmod.h:9,
>> from ./include/linux/module.h:13,
>> from ./include/linux/acpi.h:29,
>> from ./include/acpi/apei.h:9,
>> from ./include/acpi/ghes.h:5,
>> from ./include/linux/arm_sdei.h:8,
>> from arch/arm64/kernel/asm-offsets.c:10:
>> ./include/uapi/linux/sysctl.h:561:29: error: expected ‘,’ or ‘}’ before
>> ‘__attribute__’
>> NET_IPV6_TEMP_PREFERED_LFT __attribute__((deprecated)) = /* NOTYPO */
>> ^
>> scripts/Makefile.build:99: recipe for target
>> 'arch/arm64/kernel/asm-offsets.s' failed
>> make[1]: *** [arch/arm64/kernel/asm-offsets.s] Error 1
>> Makefile:1108: recipe for target 'prepare0' failed
>> make: *** [prepare0] Error 2
>>
>> It's the commit <79f0cf35dccb> ("treewide: cleanup: replace prefered with
>> preferred").
>
> After receiving a report from kisskb for failures for m68k, looking at
> http://kisskb.ellerman.id.au/kisskb/head/f3c452cfc59c817950b150b51ec2b33409d7640b/
> and doing some testing, it looks like this construct is supported by gcc-7
> and gcc-8, but not by gcc-4.6.3 and gcc-5. Don't know about gcc-6.
I guess that's a different problem than the misspelled PREFERED before the
__attribute__.
--
~Randy
Re: linux-next: Tree for Oct 23
On Wed, Oct 23, 2019 at 8:17 AM Shaokun Zhang
wrote:
> +Cc: Mark Salyzyn
>
> There is a compiler failure on arm64 platform, as follow:
> zhangshaokun@ubuntu:~/linux-next$ make -j64
> CALLscripts/atomic/check-atomics.sh
> CC arch/arm64/kernel/asm-offsets.s
> In file included from ./include/linux/sysctl.h:30:0,
> from ./include/linux/umh.h:9,
> from ./include/linux/kmod.h:9,
> from ./include/linux/module.h:13,
> from ./include/linux/acpi.h:29,
> from ./include/acpi/apei.h:9,
> from ./include/acpi/ghes.h:5,
> from ./include/linux/arm_sdei.h:8,
> from arch/arm64/kernel/asm-offsets.c:10:
> ./include/uapi/linux/sysctl.h:561:29: error: expected ‘,’ or ‘}’ before
> ‘__attribute__’
> NET_IPV6_TEMP_PREFERED_LFT __attribute__((deprecated)) = /* NOTYPO */
> ^
> scripts/Makefile.build:99: recipe for target
> 'arch/arm64/kernel/asm-offsets.s' failed
> make[1]: *** [arch/arm64/kernel/asm-offsets.s] Error 1
> Makefile:1108: recipe for target 'prepare0' failed
> make: *** [prepare0] Error 2
>
> It's the commit <79f0cf35dccb> ("treewide: cleanup: replace prefered with
> preferred").
After receiving a report from kisskb for failures for m68k, looking at
http://kisskb.ellerman.id.au/kisskb/head/f3c452cfc59c817950b150b51ec2b33409d7640b/
and doing some testing, it looks like this construct is supported by gcc-7
and gcc-8, but not by gcc-4.6.3 and gcc-5. Don't know about gcc-6.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: linux-next: Tree for Oct 23
+Cc: Mark Salyzyn
There is a compiler failure on arm64 platform, as follow:
zhangshaokun@ubuntu:~/linux-next$ make -j64
CALLscripts/atomic/check-atomics.sh
CC arch/arm64/kernel/asm-offsets.s
In file included from ./include/linux/sysctl.h:30:0,
from ./include/linux/umh.h:9,
from ./include/linux/kmod.h:9,
from ./include/linux/module.h:13,
from ./include/linux/acpi.h:29,
from ./include/acpi/apei.h:9,
from ./include/acpi/ghes.h:5,
from ./include/linux/arm_sdei.h:8,
from arch/arm64/kernel/asm-offsets.c:10:
./include/uapi/linux/sysctl.h:561:29: error: expected ‘,’ or ‘}’ before
‘__attribute__’
NET_IPV6_TEMP_PREFERED_LFT __attribute__((deprecated)) = /* NOTYPO */
^
scripts/Makefile.build:99: recipe for target 'arch/arm64/kernel/asm-offsets.s'
failed
make[1]: *** [arch/arm64/kernel/asm-offsets.s] Error 1
Makefile:1108: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
It's the commit <79f0cf35dccb> ("treewide: cleanup: replace prefered with
preferred").
Thanks,
Shaokun
On 2019/10/23 12:55, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20191022:
>
> Non-merge commits (relative to Linus' tree): 5530
> 5340 files changed, 192671 insertions(+), 90844 deletions(-)
>
>
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one. You should use "git fetch" and checkout or reset to the new
> master.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.log
> files in the Next directory. Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig. And finally, a simple boot test of the powerpc
> pseries_le_defconfig kernel in qemu (with and without kvm enabled).
>
> Below is a summary of the state of the merge.
>
> I am currently merging 310 trees (counting Linus' and 78 trees of bug
> fix patches pending for the current merge release).
>
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
>
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
>
> Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
> Gortmaker for triage and bug fixes.
>
Re: linux-next: Tree for Oct 23
Hi all, I neglected to mention that there will be no linux-next tomorrow. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpTM3JtGZFMY.pgp Description: OpenPGP digital signature
Re: linux-next: Tree for Oct 23
Hi all, I neglected to mention that there will be no linux-next tomorrow. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpTM3JtGZFMY.pgp Description: OpenPGP digital signature
Re: linux-next: Tree for Oct 23
On Thu, Oct 24, 2013 at 09:20:53AM +0200, Sedat Dilek wrote: > On Wed, Oct 23, 2013 at 5:13 PM, Thierry Reding > wrote: > > Hi all, > > > > I've uploaded today's linux-next tree to the master branch of the > > repository below: > > > > git://gitorious.org/thierryreding/linux-next.git > > > > WebGit URL? > > Browsing "https://gitorious.org/thierryreding; gives me a... > > "This Git object is too large to be displayed in the browser > > Consider cloning the repository locally and look at the object there" I should work if you go to: https://gitorious.org/thierryreding/linux-next > Thierry, you were talking about moving to a address, what > happened? I decided against it because people were starting to actively use the temporary location and I didn't want yet another change in URL to prevent testing from happening. My hope is that the next time Stephen needs a break, and provided that I'd be able and willing to volunteer for the job again, we will be better prepared and make the transition more seemless by using the standard location to begin with. Thierry pgpkSiilOeEIZ.pgp Description: PGP signature
Re: linux-next: Tree for Oct 23
On Wed, Oct 23, 2013 at 5:13 PM, Thierry Reding wrote: > Hi all, > > I've uploaded today's linux-next tree to the master branch of the > repository below: > > git://gitorious.org/thierryreding/linux-next.git > WebGit URL? Browsing "https://gitorious.org/thierryreding; gives me a... "This Git object is too large to be displayed in the browser Consider cloning the repository locally and look at the object there" Thierry, you were talking about moving to a address, what happened? - Sedat - > A next-20131023 tag is also provided for convenience. > > No new conflicts. I've fixed various build failures, so 32-bit and 64-bit > allmodconfigs build fine on x86. ARM and x86 default configurations also > build fine. Most of the patches to fix the build failures have been sent > to the respective maintainers. > > Thierry > -- > To unsubscribe from this list: send the line "unsubscribe linux-next" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 23
On Wed, Oct 23, 2013 at 5:13 PM, Thierry Reding thierry.red...@gmail.com wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git WebGit URL? Browsing https://gitorious.org/thierryreding; gives me a... This Git object is too large to be displayed in the browser Consider cloning the repository locally and look at the object there Thierry, you were talking about moving to a kernel.org address, what happened? - Sedat - A next-20131023 tag is also provided for convenience. No new conflicts. I've fixed various build failures, so 32-bit and 64-bit allmodconfigs build fine on x86. ARM and x86 default configurations also build fine. Most of the patches to fix the build failures have been sent to the respective maintainers. Thierry -- To unsubscribe from this list: send the line unsubscribe linux-next in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 23
On Thu, Oct 24, 2013 at 09:20:53AM +0200, Sedat Dilek wrote: On Wed, Oct 23, 2013 at 5:13 PM, Thierry Reding thierry.red...@gmail.com wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git WebGit URL? Browsing https://gitorious.org/thierryreding; gives me a... This Git object is too large to be displayed in the browser Consider cloning the repository locally and look at the object there I should work if you go to: https://gitorious.org/thierryreding/linux-next Thierry, you were talking about moving to a kernel.org address, what happened? I decided against it because people were starting to actively use the temporary location and I didn't want yet another change in URL to prevent testing from happening. My hope is that the next time Stephen needs a break, and provided that I'd be able and willing to volunteer for the job again, we will be better prepared and make the transition more seemless by using the standard location to begin with. Thierry pgpkSiilOeEIZ.pgp Description: PGP signature
Re: linux-next: Tree for Oct 23
On Wed, Oct 23, 2013 at 05:13:22PM +0200, Thierry Reding wrote: > Hi all, > > I've uploaded today's linux-next tree to the master branch of the > repository below: > > git://gitorious.org/thierryreding/linux-next.git > > A next-20131023 tag is also provided for convenience. > > No new conflicts. I've fixed various build failures, so 32-bit and 64-bit > allmodconfigs build fine on x86. ARM and x86 default configurations also > build fine. Most of the patches to fix the build failures have been sent > to the respective maintainers. > Build test results are a bit better than yesterday: total: 110 pass: 92 skipped: 4 fail: 14 For the qemu tests, the mips64 build still fails due to an unused variable 'usp' in arch/mips/include/asm/syscall.h, and the sh test crashes with a NULL pointer access in ata_finalize_port_ops(). Detailed results are, as always, available at http://server.roeck-us.net:8010/builders. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 23
On Wed, Oct 23, 2013 at 05:13:22PM +0200, Thierry Reding wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131023 tag is also provided for convenience. No new conflicts. I've fixed various build failures, so 32-bit and 64-bit allmodconfigs build fine on x86. ARM and x86 default configurations also build fine. Most of the patches to fix the build failures have been sent to the respective maintainers. Build test results are a bit better than yesterday: total: 110 pass: 92 skipped: 4 fail: 14 For the qemu tests, the mips64 build still fails due to an unused variable 'usp' in arch/mips/include/asm/syscall.h, and the sh test crashes with a NULL pointer access in ata_finalize_port_ops(). Detailed results are, as always, available at http://server.roeck-us.net:8010/builders. Guenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
