From: Geert Uytterhoeven <geert@linux-m68k.org> To: Masahiro Yamada <yamada.masahiro@socionext.com> Cc: Geert Uytterhoeven <geert+renesas@glider.be>, Shuah Khan <shuah@kernel.org>, Michal Marek <michal.lkml@markovi.net>, Jonathan Corbet <corbet@lwn.net>, Bamvor Jian Zhang <bamv2005@gmail.com>, Kees Cook <keescook@chromium.org>, "open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@vger.kernel.org>, Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Sam Ravnborg <sam@ravnborg.org> Subject: Re: [PATCH 00/12] selftests: Miscellaneous fixes Date: Fri, 18 Jan 2019 08:57:27 +0100 [thread overview] Message-ID: <CAMuHMdWGbJwWXMK7f10n2zPSiMEj7EHJfiK0Pj4ABHHu3f4sdw@mail.gmail.com> (raw) In-Reply-To: <CAK7LNASdA+5_pdTjr1dY-cKGSDq804Huc_CX_8-Gg+ypFCmajQ@mail.gmail.com> Hi Yamada-san, On Fri, Jan 18, 2019 at 5:15 AM Masahiro Yamada <yamada.masahiro@socionext.com> wrote: > On Mon, Jan 14, 2019 at 10:52 PM Geert Uytterhoeven > <geert+renesas@glider.be> wrote: > > This patch series contains several build fixes and cleanups for issues I > > encountered when trying to cross-build an rtctest binary in a separate > > output directory (like I use for all my kernel builds). > > Geert, > Thanks for working on this! > > My fundamental question is, > why did tools/ opt out Kbuild? Good question. I think it originally started as a separate small project. > I think lots of mess comes in > in order to support > cd tools/gpio; make > > instead of > > make tools/gpio/ > > Lots of files are duplicated in tools/build/ > in order to invent a different build system for tools/ I agree switching to kbuild would be the best solution. Unfortunately my kbuild foo is not strong enough... Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@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
WARNING: multiple messages have this Message-ID
From: geert at linux-m68k.org (Geert Uytterhoeven) Subject: [PATCH 00/12] selftests: Miscellaneous fixes Date: Fri, 18 Jan 2019 08:57:27 +0100 [thread overview] Message-ID: <CAMuHMdWGbJwWXMK7f10n2zPSiMEj7EHJfiK0Pj4ABHHu3f4sdw@mail.gmail.com> (raw) In-Reply-To: <CAK7LNASdA+5_pdTjr1dY-cKGSDq804Huc_CX_8-Gg+ypFCmajQ@mail.gmail.com> Hi Yamada-san, On Fri, Jan 18, 2019 at 5:15 AM Masahiro Yamada <yamada.masahiro at socionext.com> wrote: > On Mon, Jan 14, 2019 at 10:52 PM Geert Uytterhoeven > <geert+renesas at glider.be> wrote: > > This patch series contains several build fixes and cleanups for issues I > > encountered when trying to cross-build an rtctest binary in a separate > > output directory (like I use for all my kernel builds). > > Geert, > Thanks for working on this! > > My fundamental question is, > why did tools/ opt out Kbuild? Good question. I think it originally started as a separate small project. > I think lots of mess comes in > in order to support > cd tools/gpio; make > > instead of > > make tools/gpio/ > > Lots of files are duplicated in tools/build/ > in order to invent a different build system for tools/ I agree switching to kbuild would be the best solution. Unfortunately my kbuild foo is not strong enough... Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at 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
WARNING: multiple messages have this Message-ID
From: geert@linux-m68k.org (Geert Uytterhoeven) Subject: [PATCH 00/12] selftests: Miscellaneous fixes Date: Fri, 18 Jan 2019 08:57:27 +0100 [thread overview] Message-ID: <CAMuHMdWGbJwWXMK7f10n2zPSiMEj7EHJfiK0Pj4ABHHu3f4sdw@mail.gmail.com> (raw) Message-ID: <20190118075727.cKHOmSOa5_QLijhhbC9-8A68LXJqRnmafXdeI1NDEMY@z> (raw) In-Reply-To: <CAK7LNASdA+5_pdTjr1dY-cKGSDq804Huc_CX_8-Gg+ypFCmajQ@mail.gmail.com> Hi Yamada-san, On Fri, Jan 18, 2019 at 5:15 AM Masahiro Yamada <yamada.masahiro@socionext.com> wrote: > On Mon, Jan 14, 2019 at 10:52 PM Geert Uytterhoeven > <geert+renesas@glider.be> wrote: > > This patch series contains several build fixes and cleanups for issues I > > encountered when trying to cross-build an rtctest binary in a separate > > output directory (like I use for all my kernel builds). > > Geert, > Thanks for working on this! > > My fundamental question is, > why did tools/ opt out Kbuild? Good question. I think it originally started as a separate small project. > I think lots of mess comes in > in order to support > cd tools/gpio; make > > instead of > > make tools/gpio/ > > Lots of files are duplicated in tools/build/ > in order to invent a different build system for tools/ I agree switching to kbuild would be the best solution. Unfortunately my kbuild foo is not strong enough... Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at 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
next prev parent reply other threads:[~2019-01-18 7:57 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-14 13:51 Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 01/12] selftests: gpio-mockup-chardev: Check asprintf() for error Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-16 22:03 ` shuah 2019-01-16 22:03 ` shuah 2019-01-16 22:03 ` shuah 2019-01-14 13:51 ` [PATCH 02/12] selftests: Fix output directory with O= Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 03/12] selftests: Fix header install " Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 04/12] selftests: android: ion: Fix ionmap_test dependencies Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 05/12] selftests: seccomp: Fix test dependencies and rules Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 23:16 ` Kees Cook 2019-01-14 23:16 ` Kees Cook 2019-01-14 23:16 ` Kees Cook 2019-01-14 23:16 ` keescook 2019-01-14 13:51 ` [PATCH 06/12] selftests: lib.mk: Add rule to build object file from C source file Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 07/12] selftests: memfd: Fix build with O= Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 08/12] selftests: timestamping: Remove superfluous rules Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 09/12] selftests: sparc64: " Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 10/12] selftests: intel_pstate: Remove unused header dependency rule Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH 11/12] selftests: Add kselftest-build target Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-14 13:51 ` [PATCH/RFC 12/12] selftests: gpio: Fix building tools/gpio from kselftests Geert Uytterhoeven 2019-01-14 13:51 ` Geert Uytterhoeven 2019-01-14 13:51 ` geert+renesas 2019-01-18 4:14 ` [PATCH 00/12] selftests: Miscellaneous fixes Masahiro Yamada 2019-01-18 4:14 ` Masahiro Yamada 2019-01-18 4:14 ` Masahiro Yamada 2019-01-18 4:14 ` yamada.masahiro 2019-01-18 7:57 ` Geert Uytterhoeven [this message] 2019-01-18 7:57 ` Geert Uytterhoeven 2019-01-18 7:57 ` Geert Uytterhoeven 2019-01-18 7:57 ` geert
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAMuHMdWGbJwWXMK7f10n2zPSiMEj7EHJfiK0Pj4ABHHu3f4sdw@mail.gmail.com \ --to=geert@linux-m68k.org \ --cc=bamv2005@gmail.com \ --cc=corbet@lwn.net \ --cc=geert+renesas@glider.be \ --cc=keescook@chromium.org \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=michal.lkml@markovi.net \ --cc=sam@ravnborg.org \ --cc=shuah@kernel.org \ --cc=yamada.masahiro@socionext.com \ --subject='Re: [PATCH 00/12] selftests: Miscellaneous fixes' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.