Re: [PATCH v5 00/23] Unify vDSOs across more architectures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Feb 28, 2019 at 1:09 PM Vincenzo Frascino
<vincenzo.frascino@xxxxxxx> wrote:
>
> thank you for testing my code.
>
> On 28/02/2019 11:40, Arnd Bergmann wrote:
> > On Fri, Feb 22, 2019 at 1:25 PM Vincenzo Frascino
> > <vincenzo.frascino@xxxxxxx> wrote:
> >   ^
> >
> > I think this is all harmless, but we need to limit the set of header files
> > that can be included indirectly when compiling the vdso in arm32 mode.
> >
>
> I agree with you on the principle, but I am unable to replicate the warnings.
> Did you make any customization to the default defconfig? What is the top
> commit-id you have on your tree?

I observed this on top of v5.0-rc7 earlier, and have since rebased to
today's linux-next, where it still happens with the regular 'make defconfig',
on all compiler versions I have (4.8 through 8.1).

     Arnd



[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux