On Mon, 15 Jun 2020 at 16:15, Masahiro Yamada wrote:
>
> On Mon, Jun 15, 2020 at 7:41 PM Ard Biesheuvel wrote:
> >
> > On Mon, 15 Jun 2020 at 12:26, Ard Biesheuvel wrote:
> > >
> > > On Thu, 4 Jun 2020 at 04:20, Masahiro Yamada wrote:
> > > >
> > > > Documentation/kbuild/makefiles.rst says:
>
On Mon, Jun 15, 2020 at 7:41 PM Ard Biesheuvel wrote:
>
> On Mon, 15 Jun 2020 at 12:26, Ard Biesheuvel wrote:
> >
> > On Thu, 4 Jun 2020 at 04:20, Masahiro Yamada wrote:
> > >
> > > Documentation/kbuild/makefiles.rst says:
> > >
> > > Use of lib-y is normally restricted to `lib/` and
On Mon, 15 Jun 2020 at 12:26, Ard Biesheuvel wrote:
>
> On Thu, 4 Jun 2020 at 04:20, Masahiro Yamada wrote:
> >
> > Documentation/kbuild/makefiles.rst says:
> >
> > Use of lib-y is normally restricted to `lib/` and `arch/*/lib`.
> >
> > This is because lib-y is inteded to be hooked to
On Thu, 4 Jun 2020 at 04:20, Masahiro Yamada wrote:
>
> Documentation/kbuild/makefiles.rst says:
>
> Use of lib-y is normally restricted to `lib/` and `arch/*/lib`.
>
> This is because lib-y is inteded to be hooked to KBUILD_VMLINUX_LIBS,
> which is passed down to scripts/link-vmlinux.sh.
>
>
Documentation/kbuild/makefiles.rst says:
Use of lib-y is normally restricted to `lib/` and `arch/*/lib`.
This is because lib-y is inteded to be hooked to KBUILD_VMLINUX_LIBS,
which is passed down to scripts/link-vmlinux.sh.
Besides, lib-y is not so interesting because objects from lib-y are
5 matches
Mail list logo