From: Richard Weinberger <richard@nod.at>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, Jeff Dike <jdike@addtoit.com>,
linux-um@lists.infradead.org,
Randy Dunlap <rdunlap@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Michal Marek <michal.lkml@markovi.net>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Kbuild: fix and clean-up arch/um/Makefile
Date: Mon, 06 Aug 2018 22:54:33 +0200 [thread overview]
Message-ID: <1901723.5RX4ofS7Gn@blindfold> (raw)
In-Reply-To: <1533358023-5801-1-git-send-email-yamada.masahiro@socionext.com>
Am Samstag, 4. August 2018, 06:47:00 CEST schrieb Masahiro Yamada:
>
> 1/3 fixes the build failure reported by Randy.
> (I may have seen a similar report before, but I cannot recall it.)
>
> 2/3 and 3/3 clean-up the Makefile a bit more.
>
> I'd like to apply this series to kbuild tree.
> Ack from UML folks are appreciated.
Nice to see this fixed, Masahiro! :-)
Acked-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
next prev parent reply other threads:[~2018-08-06 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 4:47 [PATCH 0/3] Kbuild: fix and clean-up arch/um/Makefile Masahiro Yamada
2018-08-04 4:47 ` [PATCH 1/3] um: fix parallel building with O= option Masahiro Yamada
2018-08-04 4:51 ` Masahiro Yamada
2018-09-15 18:47 ` Kees Cook
2018-09-18 4:01 ` Masahiro Yamada
2018-08-04 4:47 ` [PATCH 2/3] kbuild: add %asm-generic to no-dot-config-targets Masahiro Yamada
2018-08-04 4:47 ` [PATCH 3/3] um: clean up archheaders recipe Masahiro Yamada
2018-08-05 0:58 ` [PATCH 0/3] Kbuild: fix and clean-up arch/um/Makefile Randy Dunlap
2018-08-06 20:54 ` Richard Weinberger [this message]
2018-08-08 1:24 ` Masahiro Yamada
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=1901723.5RX4ofS7Gn@blindfold \
--to=richard@nod.at \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=yamada.masahiro@socionext.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).